agentleFS
Sign inStart free
alex-mextneralex-mextner/open-remote-commander/.agents/skills/go-engineering/SKILL.md

go-engineering

Skill0 starsChanged 53 days agoApache-2.0View on GitHub

Repository-local Go architecture, testing, style and performance rules for Open Remote Commander.

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use rust-engineering.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • pirafrankSkill

    rust-engineering

    Apply pragmatic Rust engineering conventions when implementing, modifying, reviewing, or refactoring Rust code. Use for Rust CLI tools, system utilities, daemons, filesystem operations, network integrations, and security-sensitive code. Based on the official Rust guidelines and selected Google Rust Style Guide practices.

    Also in 3 projects that use this

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. cmdr-chara/chara-toolkit★ 2same name
    2. cmdr-chara/codex-toolkit★ 2same name
    3. nafeeur/MaskShift★ 2same name
    4. caseyng/Claude-skills★ 1same name
    5. fabork-security/go-engineering-skill★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use gofmt; keep packages small and cohesive.

    line 8
  2. Distinctive:

    Never start an unbounded goroutine per untrusted item.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Go engineering rules

  1. Use gofmt; keep packages small and cohesive. Composition belongs in cmd/*; reusable implementation belongs in internal/*; stable external JSON contracts belong in pkg/api/v1.
  2. Introduce interfaces only at substitution/testing boundaries. Prefer concrete return types and dependency injection through constructors.
  3. Pass context.Context as the first parameter for blocking/network operations. Propagate cancellation. Never store request contexts in structs.
  4. Errors must carry operation context with %w; compare sentinel errors with errors.Is.
  5. Never start an unbounded goroutine per untrusted item. Bound channels, payload sizes, process count and concurrent remote calls.
  6. Hot-path optimization requires a benchmark/profile. Prefer fewer allocations and streaming/bounded I/O over clever micro-optimizations.
  7. Table-driven tests for boundary cases; race detector for concurrency; fuzz parsers/path containment; integration tests for HTTP/WebSocket flows.
  8. Required checks before merge: go test ./..., go test -race ./..., go vet ./..., govulncheck ./..., lint, build.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free