go-naming

Apply Go naming conventions to packages, files, and identifiers.

Updated Mar 24, 2026

Search Tags:#golang #go #conventions #code-quality #naming #idiomatic

Ready to run

npx skills add https://github.com/1thirteeng3/greenmoire --skill go-naming-1thirteeng3

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go-naming
Source: https://github.com/1thirteeng3/greenmoire/tree/main/integrations/ragflow/.agents/skills/go-naming
Command: npx skills add https://github.com/1thirteeng3/greenmoire --skill go-naming-1thirteeng3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go naming conventions and best practices help ensure readability and maintainability by standardizing how packages, files, and identifiers are named across a codebase. This reduces cognitive load, prevents naming inconsistencies, and accelerates collaboration.

Core Features & Use Cases

Idiomatic Go naming guidance: Provides rules for package names, exported vs unexported identifiers, and file/directory naming aligned with Go community standards.
Consistent symbol naming: Recommends casing, abbreviations, and naming patterns for types, functions, variables, and constants.
Practical examples: Demonstrates naming decisions in common Go scenarios to improve code clarity and maintainability.

Quick Start

Follow the Go naming conventions to rename identifiers in your current project to idiomatic Go names.

Frequently Asked Questions about go-naming

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

FAQPage Schema

What are the idiomatic Go naming conventions for packages and exported symbols?▼

Idiomatic Go naming conventions standardize package names, exported identifiers, and file naming to improve code readability and maintainability across Go projects. These rules enforce consistent casing, abbreviations, and naming patterns aligned with community standards.

How do I apply Go naming rules to variables, constants, and functions in my codebase?▼

You apply Go naming rules by enforcing specific casing, abbreviation, and naming patterns for variables, constants, and functions within your codebase. This ensures consistent symbol naming and accelerates collaboration by reducing cognitive load.

Can I use Go naming conventions for large project directory structures and filenames?▼

Yes, Go naming conventions apply across small to large Go projects, covering filenames and directory structures. Standardizing these identifiers prevents naming inconsistencies and ensures alignment with Go community standards.

What is the best way to standardize Go code quality through identifier naming?▼

The best way to standardize Go code quality is by applying idiomatic naming rules to package, file, and symbol identifiers. This reduces cognitive load, prevents inconsistencies, and demonstrates naming decisions in common Go scenarios.

Does Go naming consistency require distinguishing between exported and unexported identifiers?▼

Yes, Go naming consistency requires enforcing export conventions by distinguishing between exported and unexported identifiers. This practice aligns with Go community standards and improves overall code clarity and maintainability.