golang-naming

Idiomatic Go naming conventions require lowercase, singular, single-word packages that avoid generic names like utils, and specific identifier rules for constructors, receivers, booleans, acronyms, and errors to ensure code reads naturally without stuttering.

To name tests and subtests in a Go project, apply standard test naming guidance for table-driven cases, subtests, and helper functions. This ensures predictable test naming that aligns with standard library style rules.

When deciding between New versus NewTypeName for Go constructors, apply idiomatic naming rules to enforce standard library style. This prevents stuttering and ensures your API design reads naturally without redundant type names.

To name error values and boolean variables in Go, follow identifier rules that enforce lowercase error strings and clear boolean prefixes like IsConnected. This avoids stuttering and matches standard library style expectations.

Yes, you can use this Skill to review and refactor existing Go code. It improves code by applying idiomatic conventions for packages, identifiers, constructors, booleans, enums, errors, and tests during your code review process.

The best way to avoid stuttering in Go package and type names is to apply standard library style rules that enforce stutter-free names. This ensures packages, types, and functions read naturally without redundant name patterns.