go-code-style

Idiomatic Go style covers formatting-adjacent decisions like early returns, switch usage, and slice initialization that gofmt cannot enforce. It guides control flow simplification, declaration choices, and function design to produce clearer, more maintainable code.

Refactor nested Go code by preferring early returns to remove unnecessary else branches and replacing long if chains with switch statements. This flattens control flow and communicates intent more clearly to reviewers.

Choose value or pointer arguments based on struct size, mutation requirements, and API consistency. Value arguments prevent unintended side effects for small structs, while pointers are necessary when the function must modify the caller's variable or handle large structures efficiently.

Initialize slices and maps using named composite literals and correct pre-allocation. Proper initialization prevents nil-map panics and brittle struct literals, ensuring your Go code follows community conventions for safe and readable data structure handling.

Yes, you can use this for Go code review on production services. It helps standardize code to match common Go community conventions by checking early returns, switch usage, composite literals, and function signatures against lintable style rules.

Yes, this requires gofmt-compatible source formatting as a baseline. It operates on formatting-adjacent decisions and control flow simplification that build upon standard gofmt output, verifying your code against lintable style rules and community conventions.