skills.rest
tamago0224
tamago0224COMMUNITY
Explore all skills by this author →
GitHub

golang-naming

Standardize Go code naming with MixedCaps and official style rules.

Updated Mar 8, 2026
Search Tags:#style#go#conventions#lint#naming#idiomatic
One-click install
npx skills add https://github.com/tamago0224/kuroshio-mta --skill golang-naming-tamago0224
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: golang-naming
Source: https://github.com/tamago0224/kuroshio-mta/tree/main/.agents/skills/golang-naming
Command: npx skills add https://github.com/tamago0224/kuroshio-mta --skill golang-naming-tamago0224

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many Go codebases suffer from inconsistent or non‑idiomatic naming, leading to confusing APIs and harder maintenance.

Core Features & Use Cases

  • Enforces MixedCaps, avoids stuttering, and prescribes constructor, interface, and error naming conventions.
  • Provides guidance on package, file, and constant naming, including acronyms and boolean fields.
  • Ideal when writing new Go code, reviewing pull requests, or refactoring existing projects to align with Go’s style guidelines.

Quick Start

Ask the golang-naming skill to evaluate the naming of your Go file and recommend idiomatic changes.

Frequently Asked Questions about golang-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 identifiers?▼

Idiomatic Go naming uses MixedCaps for identifiers, avoids stuttering in package names, and enforces proper acronym casing to improve code readability and maintainability across Go projects.

How do I name interfaces, errors, and constructors in Go code?▼

Naming interfaces, errors, and constructors in Go follows specific style rules that prescribe constructor patterns and error naming conventions to ensure APIs remain clear and consistent.

Should Go boolean fields and constants use specific naming patterns?▼

Go boolean fields should use predicate prefixes, and constants must follow standard naming rules to align with official Go style guidelines for idiomatic code presentation.

How do I check if my Go file follows official style guidelines for naming?▼

You can evaluate your Go file's naming by applying standard rules for MixedCaps, acronym casing, and package naming to recommend idiomatic changes that align with Go style guidelines.

When should I apply Go naming standards during development?▼

Apply Go naming standards when writing new Go code, reviewing pull requests, or refactoring existing projects to resolve inconsistent naming that leads to confusing APIs and harder maintenance.

Does this Go naming guidance cover test file naming conventions?▼

Yes, the Go naming guidance covers test naming decisions, providing specific conventions for test files alongside package, file, identifier, constant, and enum naming rules.

Related Skills

Explore More Software Engineering Skills→
eduardo-sleduardo-sl
64

go-coding-standards

Enforce idiomatic Go coding standards across source files and pull requests.

Community
Intermediate
CsHengCsHeng
10

language-go

Validate Go code through compilation, linting, testing, and dependency checks.

Community
Advanced
ArcadeAIArcadeAI
8

lint

Run linters and apply automatic formatting for Python, JavaScript/TypeScript, and Go projects.

Official
Intermediate
oborchersoborchers
28

casing-law

Enforce strict casing conventions across Python, TypeScript, and Go code.

Community
Intermediate