test-auditlisted
Install: claude install-skill 851-labs/codevisor
# Test Audit
Adapted from OpenClaw's `test-audit` skill (MIT,
https://github.com/openclaw/openclaw/tree/main/.agents/skills/test-audit).
This skill decides _whether_ a test earns its place. The `deterministic-tests`
skill decides _how_ to write it; apply both.
Three modes, one value bar. Authoring mode gates every new or changed test at
write time. Audit mode runs focused sweeps of tests that re-assert source,
duplicate stronger proof, couple behavior to implementation, or keep test-only
production seams alive. Continue broad audits as separate coherent follow-up
PRs; optimize for confidence, not deletion count. Campaign mode prunes one
whole subsystem's test surface (every test file a package or app area owns);
before starting one, read [CAMPAIGN.md](CAMPAIGN.md).
## Authoring gate
Before adding any test, answer four questions; a missing answer means do not
add it yet:
1. What observable behavior, invariant, or independent contract does it protect?
2. What credible regression makes it fail?
3. Why does existing coverage not already catch that failure? Each contract has
one primary test owner at the strongest boundary; another layer needs its
own distinct risk, such as a transport or lifecycle failure the owner cannot
reach. Prefer extending a table-driven case or shared fixture over a
near-duplicate test; consolidate duplicated setup in the same change.
4. Does it need a production seam (export, flag, wrapper, injection hook) that
no production caller nee