Enforces Go code style decisions that linters miss: semantic line breaking at 4+ arguments, early returns to reduce nesting, default-then-override instead of else-if chains, and named booleans for complex conditions. Built by samber to work alongside the naming and design patterns skills in the same collection. The line breaking rules are strict (one argument per line even when prompts ask for single-line code), which feels heavy-handed until you're reviewing diffs on a team. Focuses on readability over cleverness, with practical guidance on when to use var versus :=, how to handle nil slices in JSON responses, and why blank imports belong in main packages only. Includes parallelization hints for reviewing large codebases.
npx skills add https://github.com/samber/cc-skills-golang --skill golang-code-style