domains / families / software-engineering / golang-code-style

golang-code-style

separate

Golang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See `samber/cc-skills-golang@golang-naming` skill), linter configuration (→ See `samber/cc-skills-golang@golang-lint` skill), or doc comments (→ See `samber/cc-skills-golang@golang-documentation` skill).

When to use

• writing Go code
• reviewing Go code
• asking about style or clarity
• establishing project coding standards
• line length and breaking
• variable declarations
• control flow clarity
• comment usage

When not to use

• naming conventions
• linter configuration
• doc comments

Skill page

Source