golang-naming
golang-naming is an agent skill published by samber, listed under review & testing. It lives in the samber/cc-skills-golang repository, which has 3,672 GitHub stars and is licensed under MIT; we last read it on 2026-09-16.
Provides guidelines and conventions for naming Go (Golang) packages, constructors, structs, interfaces, constants, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Used for writing, reviewing, and refactoring Go code, and choosing between naming alternatives.
Install
skills is a generic installer for any repository of Claude agent skills -- it reads samber/cc-skills-golang’s own structure rather than assuming one, the same way this page reads the skill’s own SKILL.md rather than assuming a format.
npx skills add samber/cc-skills-golang
Maintenance
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.
golang-naming compared with similar skills
| Skill | Publisher | What it does | Repo stars | Last update |
|---|---|---|---|---|
| golang-naming (this page) | samber | Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors… | 3,672 | 2026-10-23 |
| golang-benchmark(same repository) | samber | Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go bench… | 3,672 | 2026-10-23 |
| golang-cli(same repository) | samber | Golang CLI application development. Use when building, modifying, or reviewing a Go CLI tool — especially for… | 3,672 | 2026-10-23 |
| golang-concurrency(same repository) | samber | Golang concurrency design — goroutine lifecycle and leak prevention, channels and `select`, channel ownership… | 3,672 | 2026-10-23 |
| golang-context(same repository) | samber | Idiomatic context.Context usage in Golang — propagation through API boundaries, cancellation, timeouts and de… | 3,672 | 2026-10-23 |
| golang-database(same repository) | samber | Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transa… | 3,672 | 2026-10-23 |
| golang-grpc(same repository) | samber | Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices… | 3,672 | 2026-10-23 |
Skills from the same repository first, then others for this job by repository stars. Figures are from each repository when we last read it.
Common questions about golang-naming
- What does golang-naming do?
- Provides guidelines and conventions for naming Go (Golang) packages, constructors, structs, interfaces, constants, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Used for writing, reviewing, and refactoring Go code, and choosing between naming alternatives.
- How do I install golang-naming?
- Run npx skills add samber/cc-skills-golang. The skills installer reads the repository’s own structure, so it works for any repository of agent skills.
- Who publishes golang-naming?
- samber.
- Is golang-naming maintained, and what licence does it use?
- Its repository has 3,672 GitHub stars and its state in our directory is listed. Its last commit we recorded was on 2026-10-23. The repository declares the MIT licence.
More agent skills for review & testing
- browser-testing-with-devtoolsby addyosmani
- code-review-and-qualityby addyosmani
- code-simplificationby addyosmani
- doubt-driven-developmentby addyosmani
- vitestby antfu
- webapp-testingby anthropic