go-naming

Enforce idiomatic Go naming conventions for identifiers across codebases.

139|17|Updated Jan 27, 2026

Search Tags:#go #code-quality #initialisms #naming #idiomatic #style-guides #mixedcaps

Ready to run

npx skills add https://github.com/cxuu/golang-skills --skill go-naming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go-naming
Source: https://github.com/cxuu/golang-skills/tree/main/skills/go-naming
Command: npx skills add https://github.com/cxuu/golang-skills --skill go-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Go developers often struggle to maintain consistent naming across packages, types, and identifiers, leading to confusion and maintenance challenges.

Core Features & Use Cases

Enforces MixedCaps style for exported identifiers and appropriate handling of initialisms.
Guides naming for packages, receivers, and avoids repetition to improve readability and reduce cognitive load.
Use cases include onboarding new contributors, code reviews, and maintaining large Go codebases.

Quick Start

Suggest idiomatic Go names for a new package, including types, functions, and variables, to ensure clarity and consistency across the codebase.

Frequently Asked Questions about go-naming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is idiomatic Go naming for variables and exported identifiers?▼

Idiomatic Go naming uses MixedCaps for exported identifiers and proper handling of initialisms to enforce clarity. It applies consistent naming conventions across packages, functions, methods, variables, constants, and receivers in a Go codebase.

How do I enforce Go naming conventions for initialisms and packages?▼

You enforce Go naming conventions by applying MixedCaps style and package naming norms aligned with Google's and Uber's style guides. This ensures consistency across types and variables, reducing cognitive load during code reviews and onboarding.

What's the best way to name Go receivers and avoid identifier repetition?▼

The best way to name Go receivers is to use concise, consistent names that avoid repetition with the package or type name. Following idiomatic style guides improves readability and reduces cognitive load across the codebase.

Does this cover edge cases for initialisms in Go code reviews?▼

Yes, it covers edge cases for initialisms in Go code reviews by providing examples and guidance. It ensures consistent handling of initialisms like HTTP or URL within MixedCaps identifiers according to established style guides.

How do I suggest idiomatic names for a new Go package during onboarding?▼

To suggest idiomatic names for a new Go package, apply package naming norms and MixedCaps style for types and functions. This ensures clarity and consistency for onboarding new contributors and maintaining large Go projects.