Golang Naming

Covers the full spectrum of Go naming conventions, from the obvious (MixedCaps, no underscores) to the stuff that actually trips people up: when to use New versus NewTypeName, why boolean fields need the is/has prefix but the zero value in enums should be StatusUnknown not StatusReady, and why error strings stay lowercase even for acronyms. Includes a quick reference table and detailed breakdowns across packages, identifiers, functions, and error types. Useful when you're in a naming debate during code review, refactoring a codebase to match Go idioms, or just want to stop second-guessing whether it should be ErrNotFound or NotFoundError. Written by samber, who maintains several Go tooling projects.

Install to Claude Code

npx -y skills add samber/cc-skills-golang --skill golang-naming --agent claude-code