Golang Skill
Go best practices, idiomatic patterns, and toolchain reference. Strictly follows Effective Go and Go Code Review Comments.
How to use this skill
Read the relevant reference file based on the user's question:
Read when writing or reviewing Go code — naming, formatting, error handling, documentation, package design.
Covers:
- Naming conventions (MixedCaps, acronyms, interface names)
- Error handling (don't panic, wrap errors, sentinel errors)
- Package design (small, focused, no circular deps)
- Documentation comments (godoc format)
- Import organization and blank imports
- Variable declaration style
- Receiver naming and type
2. Patterns
Read when implementing Go features or asking about idiomatic Go approaches.
Covers:
- Interface design (small interfaces, accept interfaces return structs)
- Concurrency (goroutines, channels, sync primitives, context)
- Error patterns (custom errors, error wrapping, errors.Is/As)
- Functional options pattern
- Table-driven tests
- Struct embedding
- init() and package initialization
- Graceful shutdown
3. Commands
Read when the user needs Go build or test commands.
- go-build — go build, cross-compilation, build tags, ldflags
- go-test — go test, coverage, benchmarks, fuzzing
Source: pkc918/reactor — distributed by TomeVault.
1---2name: golang-43description: Go coding conventions, idiomatic patterns, and CLI commands reference. Follows Effective Go and Go Code Review Comments strictly. Trigger on any Go-related question — code style, error handling, concurrency, project structure, go mod, testing, etc. Use when this capability is needed.4---56# Golang Skill78Go best practices, idiomatic patterns, and toolchain reference. Strictly follows [Effective Go](https://go.dev/doc/effective_go) and [Go Code Review Comments](https://go.dev/wiki/CodeReviewComments).910## How to use this skill1112Read the relevant reference file based on the user's question:1314### 1. [Rules](../../rules/golang/rules.md)15Read when writing or reviewing Go code — naming, formatting, error handling, documentation, package design.1617Covers:18- Naming conventions (MixedCaps, acronyms, interface names)19- Error handling (don't panic, wrap errors, sentinel errors)20- Package design (small, focused, no circular deps)21- Documentation comments (godoc format)22- Import organization and blank imports23- Variable declaration style24- Receiver naming and type2526### 2. [Patterns](references/patterns.md)27Read when implementing Go features or asking about idiomatic Go approaches.2829Covers:30- Interface design (small interfaces, accept interfaces return structs)31- Concurrency (goroutines, channels, sync primitives, context)32- Error patterns (custom errors, error wrapping, errors.Is/As)33- Functional options pattern34- Table-driven tests35- Struct embedding36- init() and package initialization37- Graceful shutdown3839### 3. Commands40Read when the user needs Go build or test commands.4142- [go-build](../../commands/golang/go-build.md) — go build, cross-compilation, build tags, ldflags43- [go-test](../../commands/golang/go-test.md) — go test, coverage, benchmarks, fuzzing4445---46> Source: [pkc918/reactor](https://github.com/pkc918/reactor) — distributed by [TomeVault](https://tomevault.io).47<!-- tomevault:4.0:skill_md:2026-06-16 -->
tomevault-io