golang-code-style

Improve Go code readability by applying human-judgment style conventions that go beyond standard formatting. The Skill enforces early returns, named booleans for complex conditions, and breaks long function calls at meaningful semantic boundaries for easier scanning and diffing.

The best way to structure Golang control flow is to prefer early returns, eliminate unnecessary else branches, use switch statements for repeated comparisons, and extract complex conditional logic into clearly named boolean variables for maintainability.

Format long Go function signatures and calls by breaking them at semantic boundaries. This approach keeps multi-line function calls grouped logically, ensuring the code remains easy to scan and diff during reviews.

Yes, you should initialize empty slices and maps explicitly in Go. This Skill requires explicit initialization and the use of named struct literals to make data structures and function parameter intent obvious to teammates.

Choose pointer or value parameters in Go functions appropriately based on function design. This Skill checks that you keep functions focused, limit parameter counts, and select pointer usage to balance performance and clarity across your service or library.

Yes, this Skill fixes code style issues that gofmt does not cover. It applies human-judgment conventions to variable declarations, control flow, file organization, and line breaking to standardize Go code when formatting alone is insufficient.