Use when asked to benchmark Go code, compare Go implementations for performance, add a fuzz test, or investigate allocations on a hot path…
When to activate: Go CLI tools, cobra, pflag, subcommands, config files, viper, shell completion, stdin/stdout pipelines
Use when writing or reviewing Go code that starts goroutines, holds a sync.Mutex/RWMutex, or closes channels - to enforce goroutine…
This skill should be used when the user asks to "add a timeout to this Go call", "why isn't context cancellation propagating", "should I…
Use when working with context.Context in Go — placement in signatures, propagating cancellation and deadlines, and storing values in…
Use when writing conditionals, loops, or switch statements in Go — including if with initialization, early returns, for loop forms, range…
Enforces professional Go programming standards including idiomatic error handling, concurrency patterns, and optimized project structures.
Use when writing or reviewing documentation for Go packages, types, functions, or methods.
Use when deciding whether to use Go generics, writing generic functions or types, choosing constraints, or picking between type aliases…
This skill should be used when the user asks to "write a gRPC service in Go", "add a gRPC interceptor", "return a gRPC status error"…
Implements production-grade Go applications using idiomatic patterns, concurrency best practices, and efficient memory management.
Use when Go interfaces including interface design, duck typing, and composition patterns.
Language-specific review guidance for Go code including idiomatic patterns, test conventions, and build commands
Run golangci-lint and fix all reported issues.
Use this skill when the user is about to launch, thinks they're ready to go live, wants a pre-launch checklist, or asks 'am I ready to…
When to activate: net/http server, HTTP handlers, middleware, ServeMux, timeouts, TLS, HTTP client in Go
When to activate: Go logging with slog, structured logging, metrics with Prometheus, distributed tracing with OpenTelemetry
Guidelines for writing doc.go files that follow official Go documentation conventions and render correctly in go doc, godoc, and pkg.go.dev.
Use the functional options pattern for flexible constructor configuration: Define interfaces where they are used, not where they are…
Adversarial review of a working-tree diff, commit range, branch, or PR before ship.
Design and bootstrap a minimal Go project from an idea or early repository.