go-naming

Go naming conventions require MixedCaps for identifiers, specific capitalization rules for initialisms, and context-aware names to avoid repetition. This ensures code clarity, consistency, and adherence to idiomatic style based on Google and Uber guides.

To name packages in Go without repetition, use context-aware naming that prevents stutter. The Skill enforces idiomatic Go rules so package names remain clear and concise without restating information already present in function or variable names.

Go constants should use MixedCaps rather than uppercase letters with underscores. This Skill enforces idiomatic Go naming standards for constants, ensuring your code aligns with established Google and Uber style guides for optimal readability.

Yes, the Uber Go style guide recommends specific receiver names for consistency. This Skill enforces naming conventions for receivers, variables, and methods, ensuring your codebase maintains clarity and follows established idiomatic Go practices.

To refactor existing Go code for idiomatic naming, apply MixedCaps rules and context-aware conventions to all identifiers. This Skill guides the transformation of packages, functions, methods, variables, and constants to meet Google and Uber style standards.

Your Go code likely fails reviews because it lacks adherence to idiomatic naming conventions like MixedCaps or proper initialism capitalization. Enforcing Google and Uber style guides ensures clarity and consistency across all identifiers.