skills.rest
Jylhis
JylhisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

golang-naming

Validate Go identifier naming against idiomatic MixedCaps conventions.

1|Updated Apr 4, 2026
Search Tags:#linting#go#conventions#code-review#naming#mixedcaps
One-click install
npx skills add https://github.com/Jylhis/claude-marketplace --skill golang-naming-jylhis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: golang-naming
Source: https://github.com/Jylhis/claude-marketplace/tree/main/plugins/golang-dev/skills/golang-naming
Command: npx skills add https://github.com/Jylhis/claude-marketplace --skill golang-naming-jylhis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go codebases often suffer from inconsistent naming, mixing snake_case, Hungarian notation, and improper acronym casing, which reduces readability and can break tooling expectations.

Core Features & Use Cases

  • Comprehensive naming guide covering packages, files, structs, interfaces, constants, errors, booleans, receivers, getters/setters, functional options, test functions, and subtests.
  • Quick reference tables for common patterns such as constructors, error variables, and enum naming.
  • Integration with linters (revive, predeclared, errname, misspell) to automatically detect violations during code review or CI pipelines.

Quick Start

Ask the golang-naming skill to analyze your Go source and provide naming recommendations.

Frequently Asked Questions about golang-naming

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

FAQPage Schema
How do I enforce Go naming conventions for mixed caps in my source files?▼

To enforce Go naming conventions, validate identifiers against idiomatic MixedCaps rules for packages, structs, interfaces, and constants. The skill flags violations like snake_case or improper acronym casing and suggests corrections without modifying the code.

What is the correct way to name errors and test functions in Go code reviews?▼

Naming errors and test functions in Go code reviews requires following specific idiomatic conventions. The skill provides targeted guidance for these elements, checking error variables and subtests to ensure they meet standard Go readability expectations.

How do I fix improper acronym casing and Hungarian notation in my Go codebase?▼

Fixing improper acronym casing and Hungarian notation involves analyzing Go source files to detect non-idiomatic patterns. The skill identifies these specific violations and provides naming recommendations to standardize identifiers to MixedCaps.

Does this Go naming linter integrate with revive and other CI pipeline tools?▼

Yes, this Go naming linter integrates with tools like revive, predeclared, errname, and misspell. It works within code review and CI pipelines to automatically detect naming convention violations across your Go source files.

Can I get naming recommendations for Go structs, interfaces, and constants without altering my code?▼

Yes, you can receive naming recommendations for Go structs, interfaces, and constants without altering your code. The skill validates naming rules and flags violations using Go tooling, ensuring your source files remain unchanged while providing guidance.

Related Skills

Explore More Software Engineering Skills→
openshift-engopenshift-eng
112

Test Structure Analysis

Analyze Go test and source files to identify coverage gaps without executing tests.

Community
Advanced
engalarengalar
1

Assess Mendix Project Quality

Assesses Mendix Studio Pro projects via automated linting, security audits, and complexity analysis.

Community
Advanced
LuigiAPCPereiraLuigiAPCPereira

golang-naming

Validate Go naming conventions using linters like revive and misspell.

Community
Advanced
deandumdeandum
3

style

Enforce language-agnostic coding style and conventions across a codebase.

Community
Intermediate