golang-benchmark
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with Prometheus runtime metrics. Also use when the developer needs deep analysis on a specific performance indicator - this skill provides the measurement methodology, while `samber/cc-skills-golang@golang-performance` provides the optimization patterns.
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/samber/cc-skills-golang /tmp/cc-skills-golang && ln -s /tmp/cc-skills-golang/skills/golang-benchmark ~/.claude/skills/golang-benchmarkFrom README
Go Benchmarking & Performance Measurement Performance improvement does not exist without measures — if you can measure it, you can improve it. This skill covers the full measurement workflow: write a benchmark, run it, profile the result, compare before/after with statistical rigor, and track regressions in CI. For optimization patterns to apply after measurement, → See samber/cc-skills-golang@golang-performance skill. For pprof on running services, → See samber/cc-skills-golang@golang-troubleshooting skill. Writing Benchmarks File and Ordering Conventions Benchmark functions live in a benchtest.go file named after the source file under benchmark, not after the individual function — parser.go -> parserbenchtest.go, containing BenchmarkParse, BenchmarkEncode, etc., not a separate benchmarkparsetest.go per function. Keeping benchmarks in their own file (instead of mixed into parsertest.go) keeps go test -bench=.