golang-naming Skill (samber): What It Does and How to Install It

Makes Claude follow Go naming conventions for packages, constructors, errors, enums, receivers, acronyms and tests when it writes or reviews code.

Installs: 41.8K; on skills.sh
Stars: 3.7K; on GitHub
Files: 6; besides SKILL.md
Updated: Nov 2026; last repo commit

golang-naming makes Claude apply Go naming rules instead of guessing. A 24-row quick-reference table covers packages, constructors, errors, booleans, enums, receivers, acronyms and test names, and a second table lists 24 common mistakes with fixes. It applies when you write, review or refactor Go code, or ask a naming question. SKILL.md says not to use it for general Go questions that do not involve naming.

Good for

Go developers choosing between names such as New and NewTypeName or ErrNotFound and NotFoundError
Reviewers who keep flagging utils packages, stuttering names and ALL_CAPS constants
Claude Code and Codex users on Go projects

Install golang-naming

Claude Code

Copy this prompt.

Install the golang-naming skill in Claude Code. Run this command:

/plugin marketplace add samber/cc
/plugin install cc-skills-golang@samber

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

The README says these skills are built as atomic, cross-referencing units, and that installing only a subset gives a partial and potentially inconsistent view of the guidelines. It recommends installing all the general-purpose skills together, which the plugin does. Its manifest lists no hooks or MCP servers, and the repo holds 46 skills. Use the skills CLI line only if you want just this one. Pick one route, not both.

From the project README. Source.

What's in the skill

When it loads

Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.

Sections in SKILL.md

Quick Reference
MixedCaps
Avoid Stuttering
Frequently Missed Conventions
Detailed Categories
Common Mistakes
Enforce with Linters
Cross-References

Key facts

Author: samber
Repository: samber/cc-skills-golang
License: MIT
Skill version: 1.2.1
Installs on skills.sh: 41,751 (Nov 2, 2026)
GitHub stars: 3,749 (Nov 2, 2026)
skills.sh audits: Gen Agent Trust Hub pass, Socket pass, Snyk pass (Nov 2, 2026)
Last repo commit: Nov 1, 2026
Files: 7 files including SKILL.md: 5 reference guides (packages and files, identifiers, functions and methods, types and errors, testing) and an evals/evals.json file
Works in: Claude Code, Codex or similar agents, for Go projects (SKILL.md compatibility line)
Needs: The Go toolchain (SKILL.md lists go as a required binary)
Allowed tools: Read, Edit, Write, Glob, Grep, Bash(go:*), Bash(golangci-lint:*), Bash(git:*), Agent

What it includes

A 24-row table of conventions, from MixedCaps and Err prefixes to enum zero values
Quick Reference
Bans underscores and ALL_CAPS in identifiers, except test subcases and generated code
MixedCaps
Drops repeated names such as http.HTTPClient, with examples for exported types
Avoid Stuttering
Constructors, boolean fields, lowercase error strings, enum zero values, subtest names
Frequently Missed Conventions
Five reference guides: packages, identifiers, functions, types and errors, tests
Detailed Categories
A 24-row table of naming mistakes and fixes, such as Url instead of URL
Common Mistakes
Points to the golang-gopls skill so a rename updates every call site
SKILL.md says a grep, sed or manual Edit rename misses call sites and interface satisfaction.
Write · Safe renames
Names revive, predeclared, misspell and errname as the linters that catch these issues
Enforce with Linters

From the official docs

Permissions

Low risk

It lets Claude edit your Go files, including renames across the workspace, and run go, golangci-lint and git commands in your project.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It edits Go files and runs go and git commands
The frontmatter allows Edit, Write and Bash for go, golangci-lint and git. Work on a branch and read the diff before you commit.
Renames can touch many files
Applying a naming fix means renaming existing identifiers. SKILL.md points to the golang-gopls skill for safe renames, so install it or review each rename.

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Turning on read-only	No read-only setting is documented in SKILL.md.
Talks to	Your AI provider receives the Go code and command output Claude reads
Sign-in and keys	SKILL.md names no account or API key.
Scopes	Claude edits Go files in your project Claude runs go, golangci-lint and git commands Renames can change identifiers across the workspace

Questions

How do I install golang-naming?

Use the install box above. The plugin route installs the whole Go skill set (46 skills in the repo), and the skills CLI route installs only this skill. Pick one so you do not get every skill twice. The README says these skills cross-reference each other and installing a subset gives a partial view.

Does golang-naming work in the Claude app?

The README documents no Claude app install, so the Claude tab in the install box is our generic zip-upload route, not a documented one. The skill reads and edits Go files and runs go commands on your machine, so Claude Code or Codex is the better fit.

Does golang-naming need an API key?

SKILL.md names no API key or account. It does need Go installed on your machine.

Is golang-naming safe to run?

It edits your Go files and runs go, golangci-lint and git commands in your project, so work on a branch and read the diff before you commit. The skill bundles no scripts: its other files are reference guides and an evals/evals.json file.

Does golang-naming rename things for me?

It can edit identifiers, but SKILL.md says a grep, sed or manual Edit rename silently misses call sites and interface satisfaction. For safe renames it points to the golang-gopls skill, and to golang-refactoring for renames at scale.

Can I ignore one of its rules?

Yes. SKILL.md says: "To ignore a rule, just add a comment to the code."

Information

updated Nov 2, 2026

Repository: samber/cc-skills-golang
Folder: skills/golang-naming

samber/cc-skills-golang skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 7

cc-skills-golang · github.com
skills CLI commands · github.com
cc-skills-golang README · github.com
plugin.json · github.com
README.md#-how-to-use · github.com
golang-naming SKILL.md · github.com
golang-naming on skills.sh · skills.sh