golang-naming

Provide Go naming convention guidelines for identifiers, constants, structs, and interfaces.

23|1|Updated May 10, 2026
One-click install
npx skills add https://github.com/berksunduri/GOPost --skill golang-naming-berksunduri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golang-naming
Source: https://github.com/berksunduri/GOPost/tree/main/.agents/skills/golang-naming
Command: npx skills add https://github.com/berksunduri/GOPost --skill golang-naming-berksunduri

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires go, revive, predeclared, misspell, errname, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps maintain consistent and readable Go code by enforcing and providing guidance on naming conventions, reducing cognitive load and improving code maintainability.

Core Features & Use Cases

  • Naming Conventions: Provides guidelines for package names, files, exported and unexported identifiers, constants, structs, interfaces, error handling, and testing.
  • Avoiding Stuttering: Ensures identifiers do not repeat package names or contextually redundant information.
  • Frequent Mistakes: Highlights common naming pitfalls and provides fixes.
  • Enforce with Linters: Recommends using linters like revive, predeclared, misspell, and errname for automated enforcement.
  • Use Case: Use this Skill when writing new Go code, reviewing or refactoring existing code, or when you're in debate about naming alternatives.

Quick Start

Use the golang-naming skill to get guidance on naming a new function in your Go code.

Frequently Asked Questions about golang-naming

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

FAQPage Schema
What are the Go naming conventions for structs, interfaces, and constants?

Go naming conventions for structs, interfaces, and constants dictate using clear, concise identifiers to improve code readability and maintainability. This Skill provides guidelines to enforce consistency and avoid common naming pitfalls like stuttering.

How do I avoid stuttering in Go package and identifier names?

To avoid stuttering in Go package and identifier names, ensure identifiers do not repeat package names or contextually redundant information. This Skill highlights frequent mistakes and provides fixes to reduce cognitive load and maintain consistency.

How do I enforce Go coding standards using linters like revive and errname?

You can enforce Go coding standards by integrating linters like revive, predeclared, misspell, and errname into your workflow. This Skill recommends these tools for automated enforcement of readability and naming conventions.

Do I need Go installed to use this naming convention guidance?

Yes, you need Go installed along with relevant linters like revive, predeclared, misspell, and errname. This Skill requires these dependencies to provide accurate naming guidance and enforce coding standards effectively.

What is the best way to name error handling variables and testing functions in Go?

The best way to name error handling variables and testing functions in Go is to follow specific conventions that ensure readability. This Skill provides targeted guidelines for naming errors and testing components to maintain code consistency.

Can this Skill help me decide between naming alternatives when refactoring Go code?

Yes, this Skill assists in deciding between naming alternatives when writing or refactoring Go code. It provides best practices for identifiers, constants, and structs to resolve debates and improve overall code maintainability.