design_patterns-hamster_style

Go naming conventions for constructors and packages are enforced by validating snake_case directories, main.go entry points, and replacing New with Make for constructors during automated code review checks.

Formatting Go code with goimports and gofumpt is executed via the just codemod-go-fmt command, which automatically enforces indentation, trailing commas, and import sorting across the repository.

This Go style guide covers error handling patterns by providing specific guidance on using alfa/errors patterns to validate consistent error handling across Go packages during code review.

Go style guides handle generics and receiver naming by enforcing SCREAMING_SNAKE_CASE for generics and requiring full type-name receivers to ensure consistency in code patterns.

This linter is specifically designed for Dodder-specific Go conventions that diverge from standard Go styles, making it unsuitable for standard Go projects outside the Dodder repository.

Go code fails build-tag usage checks when the automated validation detects non-compliant build-tag formatting or placement that does not align with the specified Go style requirements.