Test audit
Reviews a test suite for checks that prove real behaviour, and flags redundant or implementation-coupled tests worth removing.
When to use it
- A test suite is slow or noisy and you want to prune it.
- You suspect tests that only check implementation details.
- You are deciding whether a new test is worth adding.
A practical example
You ask
“Audit the checkout tests and tell me which ones actually matter.”
Your agent does
It classifies each test by the behaviour it protects and recommends what to keep, merge or delete.
What gets installed
A single instruction file, SKILL.md, which the agent reads when the skill applies.
- SKILL.md6,026 bytes
Credit and license
Written independently, inspired by the test-audit concepts in the openclaw project; no source text was copied.