agentleFS
leejianrongleejianrong/claude-skills/go-playbook/SKILL.md

go-playbook

Skill0 starsChanged 57 days agoNo licenceView on GitHub

Go-specific engineering practices that the language-agnostic dev-playbook leaves as "translate to your stack". Covers the gates that only exist in Go (-race, -count=1 against test caching, gofmt as a hard failure, cross-compile as a gate, go mod tidy drift), test layering with build tags rather than directories, interface seams and the accept-interfaces rule, the CGo versus single-binary trade-off, enforcing architectural boundaries with internal/ plus a go/parser import test, error wrapping and context discipline, and the traps that cost real hours. Use when standing up a Go project or repo; writing a Makefile, .golangci.yml, or CI workflow for Go; structuring or layering Go tests; auditing a Go repo's gates; deciding whether a dependency is worth CGo; or debugging why a Go build, test cache, or .gitignore is behaving strangely. Read alongside dev-playbook, which owns the shape; this owns the Go specifics.

  • Installs packages

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.