golang-code-style

Enforce Go code style by applying idiomatic rules for formatting, variable usage, and early returns. Prioritize gofmt or gofumpt style, break long calls at semantic boundaries, and use linters to automate consistency checks during code reviews.

Best practices for idiomatic Go code include preferring early returns over deep nesting, using switch statements instead of long if-else chains, and initializing slices and maps to non-nil to ensure predictable behavior and readability.

Review a Go file by checking it against established style guidelines for naming, composite literal usage, and function parameter counts. This produces a prioritized list of stylistic issues with concise explanations and suggested fixes for developer education.

Yes, you can use these style guidelines to configure linters and establish team conventions. It provides actionable recommendations for nil-safe slice initialization, proper := vs var usage, and line breaking that integrate directly into review workflows.

Yes, the guidance operates without external dependencies, focusing solely on source file clarity. It relies on standard Go formatting principles and practical rules like semantic line breaking and focused function design to improve maintainability.

Use early returns and semantic line breaks in Go source files to reduce inconsistent and unclear code. These practices make functions more predictable, prevent deep nesting, and significantly improve readability and review quality across the codebase.