go

What problem does it solve? Go code written without knowledge of the language's conventions often fights the ecosystem: inconsistent naming, ignored errors, oversized interfaces, and formatting debates. This Skill anchors Go development to established idioms so code reads like the rest of the Go ecosystem. ## Core Features & Use Cases - Idiomatic Style Rules: Covers naming (PascalCase vs camelCase, acronym casing like HTTP/URL/ID), package naming, getter/setter conventions, and one-method interface naming with the -er suffix. - Error Handling Patterns: Enforces explicit error checks, error wrapping with %w, sentinel errors, custom error types, and clear guidance on when panic is acceptable. - Concurrency & Tooling Guidance: Documents goroutines, channels, select, sync.WaitGroup, context.Context, and the standard toolchain (gofmt, go vet, golangci-lint, go test -race). - Use Case: When asked to refactor a Go service, the agent applies these rules automatically — replacing GetName() getters with Name(), wrapping errors with context, and verifying interface satisfaction at compile time with var _ io.Reader = (*MyReader)(nil). ## Quick Start Review my Go package for idiomatic style issues and refactor any non-idiomatic error handling, naming, or interface definitions.