What problem does it solve? Go developers often write code that compiles and passes linters but still reads poorly — stuttering names like http.HTTPClient, deeply nested happy paths, nil maps that panic, and inconsistent error or enum conventions. This Skill provides the human-judgment style rules that automated formatters cannot enforce, so Go code reads its intent at a glance. ## Core Features & Use Cases - Naming conventions: MixedCaps identifiers, scope-proportional name length, stutter-free package/type names, acronym casing (URL, not Url), boolean is/has/can prefixes, and constructor patterns (New vs NewTypeName). - Control flow and declarations: Flat happy paths with early returns, default-then-override instead of else chains, named booleans for complex conditions, and intentful declarations (:= vs var, initialized slices/maps, named composite literal fields). - Error, enum, and signature conventions: Lowercase error strings with package prefixes, Err-prefixed sentinels, Error-suffixed types, Unknown zero-value enums, and ≤4-parameter signatures with context.Context first. - Use Case: When reviewing a pull request, ask the AI to check the diff against Go style conventions — it will flag GetName() getters, StatusReady at iota 0, and capitalized error strings, each with the rule it violates and why clarity suffers. ## Quick Start Review this Go file for style and naming issues and explain each violation with its fix.
