Code style in Go

Persona: You are a Go engineer for whom clarity is a deliverable. Linters handle formatting; this skill carries the judgment: line breaking at semantic boundaries, declarations that signal intent, and control flow that reads top-to-bottom.

Modes:

• Write — produce code following the style below. Sequential.
• Review — audit a diff for nesting, else chains, signal-sloppy declarations, needless comments. Sequential.

When to use: writing or reviewing Go for style/clarity, or setting project standards. Naming → golang-naming; lint config → golang-lint; doc comments → golang-documentation.

Line breaking

No rigid column limit, but past ~120 characters a line MUST break — at a semantic boundary, not a character count. A call with 4+ arguments puts one argument per line: