use-modern-go
Skill868 starsChanged 13 days agoApache-2.0View on GitHub
Apply modern Go syntax guidelines based on the project's Go version. Use whenever writing, editing, or reviewing Go (.go) code - not only when explicitly asked for guidelines.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- compozy/compozytheir own version, first seen Nov 13, 2026
- whz1106/whz-harnesstheir own version, first seen Nov 1, 2026
- agentstation/skillstheir own version, first seen Oct 13, 2026
- ardanlabs/servicetheir own version, first seen Oct 8, 2026
- stackrox/stackroxtheir own version, first seen Oct 8, 2026
- JetBrains/go-modern-guidelinestheir own version, first seen Aug 30, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- ardanlabs/service★ 4.1ksame name
- JetBrains/go-modern-guidelines★ 3.6ksame name
- compozy/compozy★ 2.9ksame name
- stackrox/stackrox★ 1.3ksame name
- whz1106/whz-harness★ 2same name
- agentstation/skills★ 1same name
- xingkaixin/skills★ 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 repository5 other files it gives its agents.
- .agents/default/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- kronk-pr-reviewSkill
- kronk-service-architectureSkill
- probing-kronkSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
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
- Very specific: line 8
Before writing Go, run on the file/dir being edited (<skill> = this file's dir):
“Common” is measured: kept by at least 6 in 10 of the 7 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.
Files
Modern Go
Before writing Go, run on the file/dir being edited (<skill> = this file's dir):
- sh:
sh <skill>/scripts/guidelines.sh <path> - PowerShell:
pwsh -NoProfile -ExecutionPolicy Bypass -File <skill>/scripts/guidelines.ps1 <path>(nopwsh: usepowershell, Windows PowerShell 5.1)
It prints go 1.XX + the guidelines for that version. Read all of it, unfiltered. Never detect the version yourself; re-run per module.
go 1.XX: say only "This project is using Go X.XX, so I'll use modern Go features up to that version. Let me know to target a different one."- Otherwise: say "Could not detect Go version.", ask "Which Go version should I target?" [1.26] / [1.27], re-run with
--go X.Y(PowerShell:-Go X.Y).
Apply every guideline; never use newer features. "details X" = section X of <skill>/references/details.md.
Modernizing existing code: if the installed toolchain (go version) is 1.26+, run go fix on its packages before reading their files (details "go fix"); otherwise apply the guidelines by hand.
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.

