lang-go
Skill5 starsChanged 46 days agoMITView on GitHub
use this when the change is Go but it is unclear which Go skill to load — routes to golang-safety, golang-testing, or golang-security. do not use as a fourth Go body. do not use for other languages.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- maintainers/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- buying-researcherSkill
- cursor-cloud-agents-whenSkill
- debug-anthropicSkill
- debug-pocockSkill
- debugSkill
- discover-the-ideaSkill
- docs-google-styleSkill
- golang-safetySkill
- golang-securitySkill
- golang-testingSkill
- grok-acpSkill
- host-config-pyinfraSkill
- lang-cppSkill
- lang-csharpSkill
- lang-cSkill
- lang-dartSkill
- lang-dockerSkill
- lang-javaSkill
- lang-js-tsSkill
- lang-kotlinSkill
- lang-luaSkill
- lang-makefileSkill
- lang-phpSkill
- lang-powershellSkill
- lang-protobufSkill
- lang-pythonSkill
- lang-rubySkill
- lang-rustSkill
- lang-shellSkill
- lang-sqlSkill
- lang-swiftSkill
- lang-terraformSkill
- language-routerSkill
- lang-web-markupSkill
- modern-pythonSkill
- pr-reviewSkill
- sdlc-artifactsSkill
- sdlc-onboardingSkill
- security-hardeningSkill
- shell-safetySkill
- tddSkill
- tracker-sdlcSkill
- ui-craftSkill
- ux-designSkill
- verify-before-doneSkill
- yagniSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
This id routes: Do not remint Go advice. No scripts/.
- Very specific: line 29
Add staticcheck / errcheck when tester already wired them.
- Distinctive: line 35
No goroutine without a documented lifetime (return, ctx cancel, or WaitGroup).
- Very specific: line 36
No string-built SQL or os/exec from concatenated input.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Go (router)
This id routes. Do not remint Go advice. No scripts/.
At most one language skill per turn, and the process skills that may load with it: language-router Iron law, Load-with list.
Iron law
Never write a parallel Go guide.
Load
Which Go skill loads: the Go row in language-router Map.
Then stop. Apply that skill.
Combined verify (after the chosen skill)
gofmt -l .
go test ./...
go test -race ./...Add staticcheck / errcheck when tester already wired them. Read the output.
Combined PR checklist
- Errors wrapped with
%w; compared witherrors.Is/As, not==. context.Contextis first param and is plumbed, not stored on structs.- No goroutine without a documented lifetime (return, ctx cancel, or WaitGroup).
- No string-built SQL or
os/execfrom concatenated input. - Tables in
_test.gofor the new behavior.
Never
- A new
lang-gobody that copies samber or Effective Go into this repo. npx/ marketplace install ofsamber/cc-skills-golang.
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
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.

