Modern Go Guidelines CLI
Always write modern, idiomatic Go code. Use the Modern Go Guidelines CLI as the source of truth for modern Go idioms that may be newer than your knowledge cutoff.
Command:
- Linux or macOS:
sh "<skill-dir>/scripts/run-tool.sh" - Windows PowerShell:
& '<skill-dir>\scripts\run-tool.ps1'
First run and approvals:
On first use, the wrapper installs the Modern Go Guidelines CLI in a local cache directory.
Subcommands:
listexplain
Before editing Go code:
-
Call the wrapper's
listsubcommand for the relevant Go file.Prefer passing the file you are about to edit:
On Windows, use the PowerShell wrapper with the same arguments.
The CLI resolves the applicable Go version from go.mod, go.work, the local Go toolchain, or an explicit override.
-
If the target Go version is already known, you may pass it directly:
-
Read the complete list output before deciding which guidelines apply.
The list output is ordered newest first. Read the full output because older supported guidelines may still apply.
Do not pipe the output through head, tail, grep, sed, or any other truncating/filtering command. Important guidelines may otherwise be missed.
-
Treat returned guidelines as authoritative for modern Go style choices in code you are editing.
If a guideline applies, follow it even when nearby code or repository convention uses an older pattern. Skip it only when it would not compile, would change behavior, or clearly does not match the edited code. Before skipping a returned guideline that seems relevant, call the wrapper's
explainsubcommand for that guideline ID.
Call explain only when a specific guideline may apply and you need the detailed explanation or examples. Request only the guideline IDs you intend to evaluate or apply:
Multiple guideline IDs may be requested as positional arguments:
Do not call explain without guideline IDs. Use list first to discover the short guideline list for the target Go version, then call explain for the specific returned IDs that need more context.
