Purpose
Make concurrency changes verifiable, not hope-driven.
When to use
Use this skill when touching:
- •C/C++ concurrency primitives
- •shared mutable state with locks or atomics
- •code paths with plausible races or deadlocks
How to use
- •Open
references/thread-safety-tooling.md. - •Choose verification stack (TSan / static thread-safety analysis / stress tests).
- •Provide reproducible commands or CI steps (placeholders if repo differs).
- •Define a minimal stress scenario (what to load; what to assert).
- •Record known limitations and suppression strategy (avoid blanket suppressions).
Output expectation
- •Produce a Concurrency Verification Matrix:
- •Tool → What it catches → How to run → Cost/limits