Agent skill

Go Naming

A skill your agent uses when naming any Go identifier — packages, types, functions, methods, variables, constants, or receivers — to ensure idiomatic, clear names.

Apache-2.0Auto-check passedDevelopment

Install Go Naming

skills CLI

$ npx skills add cxuu/golang-skills --skill go-naming -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install cxuu/golang-skills go-naming --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/go-naming .claude/skills/go-naming && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "go-naming" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-naming into .claude/skills/go-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-naming", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/cxuu/golang-skills/tree/main/skills/go-naming

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add cxuu/golang-skills --skill go-naming -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install cxuu/golang-skills go-naming --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/go-naming .agents/skills/go-naming && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "go-naming" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-naming into .agents/skills/go-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-naming", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add cxuu/golang-skills --skill go-naming -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install cxuu/golang-skills go-naming --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/go-naming .cursor/skills/go-naming && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "go-naming" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-naming into .cursor/skills/go-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-naming", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/cxuu/golang-skills.git --path skills/go-naming

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add cxuu/golang-skills --skill go-naming -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install cxuu/golang-skills go-naming --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/go-naming .gemini/skills/go-naming && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "go-naming" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-naming into .gemini/skills/go-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-naming", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install cxuu/golang-skills go-naming

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add cxuu/golang-skills --skill go-naming -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/go-naming .github/skills/go-naming && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "go-naming" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-naming into .github/skills/go-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-naming", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add cxuu/golang-skills --skill go-naming -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install cxuu/golang-skills go-naming --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/go-naming .opencode/skills/go-naming && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "go-naming" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-naming into .opencode/skills/go-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-naming", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: go-naming
GitHub stars: 172
Token cost: ~1.7k tokens
SKILL.md length: 582 words
Files: 5 (incl. scripts, references)
Skills in repo: 20
Repo updated: Jun 20, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses when naming any Go identifier — packages, types, functions, methods, variables, constants, or receivers — to ensure idiomatic, clear names.

Naming any Go identifier — packages
SKILL.md covers Resource Routing, Core Principle, Naming Decision Flow and MixedCaps (Required), plus 11 more sections
Runs Shell scripts from its folder; calls bash and go
Receivers — to ensure idiomatic

What it does

Go Naming is an agent skill from cxuu/golang-skills. Use when naming any Go identifier — packages, types, functions, methods, variables, constants, or receivers — to ensure idiomatic, clear names. Also use when a user is creating new types, packages, or exported APIs, even if they don't explicitly ask about naming conventions. Does not cover package organization (see go-packages).

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/IDENTIFIERS.md`, `references/REPETITION.md` and `references/VARIABLES.md`).

It sits in Development. The repository describes itself as: AI Agent Skills for idiomatic, production-ready Go code, distilled from Google, Uber, Community. The licence is Apache-2.0.

When your agent uses it

Naming any Go identifier — packages
Receivers — to ensure idiomatic
A user is creating new types
Even if they dont explicitly ask about naming conventions

Example prompts

“/go-naming”

Requirements

A Bash shell
Pre-approved tools (allowed-tools): Bash(bash:*)

What it can do on your machine

Read from SKILL.md and the folder at commit 91f0c2e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash(bash:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- bash
- go
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Go Naming loads about 1.7k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 582 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~85
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from cxuu/golang-skills at commit 91f0c2e, republished under its Apache-2.0 licence (© cxuu). 582 words, ~1,673 tokens.

Download SKILL.mdSave it as .claude/skills/go-naming/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: go-naming
description: Use when naming any Go identifier — packages, types, functions, methods, variables, constants, or receivers — to ensure idiomatic, clear names. Also use when a user is creating new types, packages, or exported APIs, even if they don't explicitly ask about naming conventions. Does not cover package organization (see go-packages).
allowed-tools: Bash(bash:*)

Go Naming Conventions

Resource Routing

scripts/check-naming.sh - Run when checking SCREAMING_SNAKE_CASE constants, Get-prefixed getters, generic package names, or receivers named this/self.
references/IDENTIFIERS.md - Read when choosing names for initialisms, exported identifiers, or package-level symbols.
references/REPETITION.md - Read when names repeat package, receiver, type, or local context.
references/VARIABLES.md - Read when choosing local variable names, receiver names, or loop identifiers.

Core Principle

Names should:

Not feel repetitive when used
Take context into consideration
Not repeat concepts that are already clear

Naming is more art than science—Go names tend to be shorter than in other languages.

Naming Decision Flow

What are you naming?
├─ Package       → Short, lowercase, singular noun (no underscores, no mixedCaps)
├─ Interface     → Method name + "-er" suffix when single-method (Reader, Writer)
├─ Receiver      → 1-2 letter abbreviation of type (c for Client); consistent across methods
├─ Constant      → MixedCaps; use iota for enums; no ALL_CAPS
├─ Exported func → Verb or verb-phrase in MixedCaps; no Get prefix for getters
├─ Variable      → Length proportional to scope distance
│                  ├─ Tiny scope (1-7 lines) → single letter (i, n, r)
│                  ├─ Medium scope           → short word (count, buf)
│                  └─ Package-level / wide   → descriptive (userAccountCount)
└─ Any name      → Check: does it repeat package name or context? If yes, shorten it

MixedCaps (Required)

Normative: All Go identifiers must use MixedCaps.

Underscores are allowed only in: test functions (TestFoo_InvalidInput), generated code, and OS/cgo interop.

Package Names

Normative: Packages must be lowercase with no underscores.

Short, lowercase, singular nouns. Avoid generic names like util, common, helper — prefer specific names: stringutil, httpauth, configloader.

// Good: user, oauth2, tabwriter
// Bad:  user_service, UserService, count (shadows var)

Interface Names

Advisory: One-method interfaces use "-er" suffix.

Name one-method interfaces by the method plus -er: Reader, Writer, Formatter. Honor canonical method names (Read, Write, Close, String) and their signatures.

Receiver Names

Normative: Receivers must be short abbreviations, used consistently.

One or two letters abbreviating the type, consistent across all methods: func (c *Client) Connect(), func (c *Client) Send(). Never use this or self.

Constant Names

Normative: Constants use MixedCaps, never ALL_CAPS or K prefix.

Name constants by role, not value: MaxRetries not Three, DefaultPort not Port8080.

const MaxPacketSize = 512
const defaultTimeout = 30 * time.Second

Initialisms and Acronyms

Normative: Initialisms maintain consistent case throughout.

Initialisms (URL, ID, HTTP, API) must be all uppercase or all lowercase: HTTPClient, userID, ParseURL() — not HttpClient, orderId, ParseUrl().

Function and Method Names

Advisory: No Get prefix for simple accessors; use verb-like names for actions.

Getter for field owner is Owner(), not GetOwner(). Setter is SetOwner(). Use Compute or Fetch for expensive operations.

When functions differ only by type, include type at the end: ParseInt(), ParseInt64().

Variable Names

Variable naming balances brevity with clarity. Key principles:

Scope-based length: Short names (i, v) for small scopes; longer, descriptive names for larger scopes
Single-letter conventions: Use familiar patterns (i for index, r/w for reader/writer)
Avoid type in name: Use users not userSlice, name not nameString
Prefix unexported globals: Use _ prefix for package-level unexported vars/consts to prevent shadowing

for i, v := range items { ... }           // small scope
pendingOrders := filterPending(orders)    // larger scope
const _defaultPort = 8080                 // unexported global

Show full SKILL.md (219 more words)Show less

Avoiding Repetition

Go names should not feel repetitive when used. Consider the full context:

Package + symbol: widget.New() not widget.NewWidget()
Receiver + method: p.Name() not p.ProjectName()
Context + type: In package sqldb, use Connection not DBConnection

Avoid Built-In Names

Never shadow Go's predeclared identifiers (error, string, len, cap, append, copy, new, make, etc.) as variable, parameter, or type names.

For detailed guidance: See go-declarations — "Avoid Using Built-In Names" section.

Quick Reference

Element	Rule	Example
Package	lowercase, no underscores	`package httputil`
Exported	MixedCaps, starts uppercase	`func ParseURL()`
Unexported	mixedCaps, starts lowercase	`func parseURL()`
Receiver	1-2 letter abbreviation	`func (c *Client)`
Constant	MixedCaps, never ALL_CAPS	`const MaxSize = 100`
Initialism	consistent case	`userID`, `XMLAPI`
Variable	length ~ scope size	`i` (small), `userCount` (large)
Built-in names	Never shadow predeclared identifiers	See `go-declarations`

Validation: After renaming identifiers, run bash scripts/check-naming.sh to verify no naming anti-patterns remain. Then run go build ./... to confirm the rename didn't break anything.

Interface naming: See go-interfaces when naming interfaces with the -er suffix or choosing receiver types
Package naming: See go-packages when naming packages, avoiding util/common, or resolving import collisions
Error naming: See go-error-handling when naming sentinel errors (ErrFoo) or custom error types
Declaration scope: See go-declarations when variable name length depends on scope or when avoiding built-in shadowing
Style principles: See go-style-core when balancing clarity vs concision in identifier names

Files

SKILL.md and 4 other files (scripts, references) in skills/go-naming of cxuu/golang-skills.

SKILL.md
references/IDENTIFIERS.md
references/REPETITION.md
references/VARIABLES.md
scripts/check-naming.sh

Open the folder on GitHubat commit 91f0c2e

Compare with similar skills

Go Naming next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Go Naming compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Go Naming this skillcxuu/golang-skills	172	—	~1.7k	Automated safety check: Pass	Apache-2.0	3 mo ago
Vercel Composition Patternssupabase/supabase	111k	58 repos	~726	Automated safety check: Pass	MIT	today
Finishing a Development Branchobra/superpowers	297k	5 repos	~1.9k	Automated safety check: Pass	MIT	today
Typescript Advanced Typesrolling-scopes/rsschool-app	10k	25 repos	~4.2k	Automated safety check: Pass	MPL-2.0	5 days ago
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	2 days ago
Code Review ChecklistshareAI-lab/learn-claude-code	78k	5 repos	~1.1k	Automated safety check: Pass	MIT	11 days ago

Similar skills

Vercel Composition Patterns
supabase/supabase
Official
React composition patterns that scale. An agent skill from supabase/supabase.
111k GitHub starsUsed in 58 repos~726 tokens
DevelopmentAuto-check passed
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
297k GitHub starsUsed in 5 repos~1.9k tokens
DevelopmentAuto-check passed
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
10k GitHub starsUsed in 25 repos~4.2k tokens
DevelopmentAuto-check passed
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
69k GitHub starsUsed in 3 repos~4.2k tokens
DevelopmentAuto-check passed
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
78k GitHub starsUsed in 5 repos~1.1k tokens
DevelopmentAuto-check passed
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
32k GitHub starsUsed in 4 repos~3.3k tokens
DevelopmentAuto-check passed

Questions about Go Naming

What does Go Naming do?

A skill your agent uses when naming any Go identifier — packages, types, functions, methods, variables, constants, or receivers — to ensure idiomatic, clear names. Go Naming is an agent skill from cxuu/golang-skills. Use when naming any Go identifier — packages, types, functions, methods, variables, constants, or receivers — to ensure idiomatic, clear names.

When should I use Go Naming?

Go Naming fits situations like: naming any Go identifier — packages; receivers — to ensure idiomatic; A user is creating new types; even if they dont explicitly ask about naming conventions.

How do I install Go Naming in Claude Code?

Run `npx skills add cxuu/golang-skills --skill go-naming -a claude-code`. Or copy the skill folder (skills/go-naming in cxuu/golang-skills) into .claude/skills/go-naming in your project. Claude Code loads it when a task matches its description.

How do I install Go Naming in Codex?

Run `npx skills add cxuu/golang-skills --skill go-naming -a codex`. Or copy the skill folder (skills/go-naming in cxuu/golang-skills) into .agents/skills/go-naming in your project. Codex loads it when a task matches its description.

Can I use Go Naming in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cxuu/golang-skills --skill go-naming -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/go-naming, .gemini/skills/go-naming, .github/skills/go-naming and .opencode/skills/go-naming in your project.

What does Go Naming need to run?

Going by SKILL.md and its folder, Go Naming needs a shell for the scripts in its folder and the command-line tools its instructions call (bash and go). Our summary lists: A Bash shell. Its frontmatter pre-approves these tools: Bash(bash:*).

Does Go Naming access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Go Naming safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Go Naming use?

Go Naming is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Go Naming use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.

What are the alternatives to Go Naming?

Skills that share tags, products or a category with Go Naming: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Go Naming?

cxuu (a GitHub user) maintains it in cxuu/golang-skills, which has 172 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on June 20, 2026.

Source: cxuu/golang-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Go Naming

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Go Naming Conventions

Resource Routing

Core Principle

Naming Decision Flow

MixedCaps (Required)

Package Names

Interface Names

Receiver Names

Constant Names

Initialisms and Acronyms

Function and Method Names

Variable Names

Avoiding Repetition

Avoid Built-In Names

Quick Reference

Related Skills

Files

Compare with similar skills

Similar skills

More from cxuu/golang-skills

Related

Questions about Go Naming