golang-code-style
Installation
SKILL.md
Adapted from
samber/cc-skills-golang@golang-code-style. Pair withgolang-common-practicefor verification and cross-reference guidance.
Go Code Style
Style rules that require human judgment — linters handle formatting, this skill handles clarity. For naming see golang-naming skill; for design patterns see golang-design-patterns skill; for struct/interface design see golang-structs-interfaces skill.
"Clear is better than clever." — Go Proverbs
When ignoring a rule, add a comment to the code.
Line Length & Breaking
No rigid line limit, but lines beyond ~120 characters MUST be broken. Break at semantic boundaries, not arbitrary column counts. Function calls with 4+ arguments MUST use one argument per line — even when the prompt asks for single-line code: