Lean and operational with no padding about what a race detector is; it opens by distinguishing the two failure classes and proceeds straight into executable steps, so every token earns its place.

Provides fully executable bash, Go, and CI YAML blocks (e.g. `go test -race -count=10 -cpu=1,2,4 ./...`, `defer goleak.VerifyNone(t)`, the GORACE options table) that are copy-paste ready rather than pseudocode.

Seven clearly sequenced steps with feedback checkpoints for the CI gate (timeout budgeting, `if: failure()` artifact upload), plus an anti-patterns table and a limitations section covering false positives and retry behavior.

The body is an overview that offloads the detailed goleak filter catalog to references/goleak-filter-options.md, which is a real, one-level-deep, clearly signaled reference.

Lists multiple concrete actions in third person ('instrument with `go test -race`', 'read race reports', 'configure GORACE options', 'stress with `-count`/`-cpu`', 'detect goroutine leaks with go.uber.org/goleak', 'gate both checks in CI'), matching the multi-action anchor rather than the domain-only level 2.

Explicitly answers both what (the colon-separated action list) and when ('Use when a Go service has shared state accessed by concurrent goroutines, when a race-related incident needs a regression harness, or when adding `-race` to a CI matrix for a Go module'), matching the score-3 anchor.

Natural terms a user would say ('Go race detector', 'goroutine-leak', 'shared state', 'concurrent goroutines', 'race-related incident', 'CI matrix', '-race') give good coverage of common phrasings.

A clear Go-specific niche with an explicit boundary clause ('Does not cover barrier-based deterministic interleaving... use race-condition-test-author for that') actively disambiguates from a sibling skill, making wrong-skill triggering unlikely.