go-benchmarklisted
Install: claude install-skill ValentinNikolaev/agent-skills
# Go Benchmark
Measure a named Go behavior under controlled conditions. Return evidence for a performance claim rather than assuming that fewer allocations or shorter code makes the product faster.
## Route precisely
- Use when asked to design/write a benchmark, measure a hot path, interpret an existing profile, or compare named implementations.
- Use `code-review` for potential defects in a diff, `debugging-and-error-recovery` for an unexplained failing or hanging program, and `prove-checks` for whether a passing check can detect its claimed defect.
- Keep production optimization, dependency installation, release publication, and CI authoring outside this workflow unless separately requested. Do not launch agents or create worktrees automatically.
## Establish the experiment
1. Read repository instructions, working-tree state, `go.mod`/`go.work`, benchmark source, and callers. Record revision/local changes, supported Go version, actual toolchain, OS/architecture, hardware, GOMAXPROCS, build flags/tags, data size, and relevant dependency/configuration versions.
2. Name the operation, representative workload, metric, desired decision, and correctness invariant. Separate microbenchmark throughput/allocations from end-to-end latency or a product requirement. If target, fixture, or baseline is unknown, resolve it before expensive measurement.
3. Inspect benchmark setup, timed work, input reuse, result consumption, parallelism, and possible compiler elimination. Use version-s