Golang Pro guides Claude through Go work in six steps: analyze the architecture, design small interfaces, implement with error wrapping and context propagation, lint, optimize with pprof and test with the race detector. Each step names a command to run before moving on, such as go vet and golangci-lint.
Five reference files cover concurrency patterns, interface design, generics, testing and benchmarking, and project structure with modules, a Makefile and a multi-stage Dockerfile.
What You Get
- Concurrent code with worker pools, fan-out and fan-in, pipelines, semaphores and rate limiting
- Small interfaces, functional options and dependency injection written for easy mocking
- Generic functions and types with constraints and type inference
- Table-driven tests, benchmarks, fuzz tests and race-detector runs
- A module layout with cmd, internal and pkg folders, go.work workspaces and build tooling
Common Use Cases
- Writing a concurrent pipeline that shuts down cleanly on cancellation
- Building a gRPC or REST microservice with configuration from environment variables
- Profiling a slow Go service with pprof and removing allocations
- Adding table-driven tests, fuzzing and coverage to an existing package
- Setting up a Go monorepo with workspaces and a Docker build
What Makes It Unique
The workflow makes lint and race checks gates between steps: go vet before moving on, golangci-lint with every issue fixed, and a passing race detector before committing. Its constraints ban common Go mistakes such as goroutines without a lifecycle, ignored errors and panic for normal failures, and the concurrency reference writes even idle pipeline stages to stop on cancellation.
Under The Hood
The skill is a SKILL.md with five reference files and no scripts, and the references load by topic. The workflow tells the agent to run go vet, golangci-lint and go test with the race flag, so it uses the shell and writes Go source and test files. The references show go get, go install and go mod commands that download modules from the network, a Makefile, a multi-stage Dockerfile and build commands that read git state for version strings. Example code reads database and cache credentials from environment variables. The skill does not tell the agent to fetch web pages.