golang-naming

Validate Go naming conventions using linters like revive and misspell.

Updated Jun 27, 2026

Search Tags:#linting #code style #naming conventions #Go #Go naming

Ready to run

npx skills add https://github.com/LuigiAPCPereira/evolutiondocs --skill golang-naming-luigiapcpereira

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers adhere to Go's naming conventions, reducing confusion and ensuring code clarity.

Core Features & Use Cases

Naming Conventions: Guidelines for packages, files, variables, types, constants, errors, interfaces, methods, and more.
Quick Reference: Tables summarizing conventions for different elements in Go.
Anti-Patterns: Identification of common mistakes in Go naming.
Enforcement: Linters for enforcing naming conventions.

Quick Start

Run the 'golang-naming' skill to review the naming conventions for 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 standard Go naming conventions for packages, variables, and interfaces?▼

Go naming conventions require clear, idiomatic names for packages, variables, and interfaces to ensure code clarity. This Skill provides specific guidelines and quick reference tables summarizing the correct naming patterns for these elements.

How do I enforce Go naming conventions and identify anti-patterns in my project?▼

You can enforce Go naming conventions by running automated linters like 'revive', 'predeclared', 'misspell', and 'errname'. This Skill applies these tools to identify anti-patterns and ensure consistent, idiomatic code across any Go project.

Do I need to install specific linters to check Go code style and naming?▼

Yes, validating Go code style requires installing linters such as 'revive', 'predeclared', 'misspell', and 'errname'. These dependencies enable the automated checks needed to enforce the naming conventions and catch common mistakes.

What is the best way to check for misspelled identifiers and predeclared name shadowing in Go?▼

The best way to check for predeclared name shadowing and misspelled identifiers is using the 'predeclared' and 'misspell' linters. This Skill integrates these tools to automatically validate your Go naming and prevent common errors.

Why does my Go linter flag certain variable and error naming as anti-patterns?▼

Linters flag Go naming anti-patterns because they violate established conventions for variables and errors, reducing code clarity. This Skill identifies these common mistakes and provides reference guidelines to correct them.