skills.rest
lazygophers
lazygophersOFFICIAL
Explore all skills by this author →
WebsiteGitHub

naming

Enforce Go naming conventions for variables, functions, types, and packages.

4|2|Updated Dec 28, 2025
Search Tags:#best practices#code style#golang#go#programming#naming conventions
One-click install
npx skills add https://github.com/lazygophers/ccplugin --skill naming-lazygophers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: naming
Source: https://github.com/lazygophers/ccplugin/tree/main/plugins/languages/golang/skills/naming
Command: npx skills add https://github.com/lazygophers/ccplugin --skill naming-lazygophers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces consistent and idiomatic naming conventions in Go code, preventing common errors and improving code readability and maintainability.

Core Features & Use Cases

  • Standardized Naming: Ensures adherence to PascalCase for exported entities, camelCase for private ones, and UPPER_CASE for constants.
  • Field Naming Guidelines: Provides specific rules for ID, time, status, and boolean fields.
  • Function Naming: Guides on using prefixes like Get, List, Count, Check, Is, and Has.
  • Receiver Naming: Mandates the use of p for receivers.
  • Use Case: When writing new Go code or reviewing existing code, use this Skill to ensure all identifiers follow the established best practices, making the codebase cleaner and easier to understand for all developers.

Quick Start

Apply the Go naming conventions to the provided code snippet.

Frequently Asked Questions about naming

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

FAQPage Schema
What are the Go naming conventions for exported functions and private variables?▼

Go naming conventions mandate PascalCase for exported entities and camelCase for private variables. This standardization improves code readability and maintainability across collaborative projects.

How do I name receiver variables in Go code?▼

Receiver naming in Go code should use the letter 'p' for consistency. This standardization ensures all method receivers across the codebase follow idiomatic Go style for improved collaboration.

What prefixes should I use for Go function names?▼

Go function naming should use specific prefixes like Get, List, Count, Check, Is, and Has. These prefixes clearly indicate the function's purpose, making the codebase easier to understand for all developers.

Are there specific Go naming rules for ID, time, and boolean fields?▼

Go naming conventions provide specific rules for ID, time, status, and boolean fields. Following these guidelines ensures adherence to idiomatic Go style and improves overall code quality.

How do I enforce consistent code style for Go programming?▼

You can enforce Go programming code style by applying naming conventions to your code snippets. This process checks identifiers against established best practices for variables, functions, types, constants, and packages.

Related Skills

Explore More Software Engineering Skills→
1thirteeng31thirteeng3

go-naming

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

Community
Intermediate
AngelWings1997AngelWings1997

go-code-review

Enforce gofmt, go vet, and golangci-lint checks during Go code reviews.

Community
Intermediate
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic
t-stringst-strings

Global Code Style

Enforce global code style guidelines when editing or generating code.

Official
Basic