test-audit

Installation
SKILL.md

Test Audit

A suite is measured by one thing: it goes red when the code is wrong. A test that cannot go red is dead code with a runtime cost, and a test that goes red on a refactor cements the implementation. This skill removes both, writes the tests a caller would want, and then proves the result by breaking the code on purpose.

Scope: $ARGUMENTS. Empty means the tests that the uncommitted diff touches, plus the seams the diff changed that have no test. A path means every test in it and every public seam in it. A git range means the same for the changed files.

The rules and examples are in ${CLAUDE_SKILL_DIR}/../clean-code/TESTS.md; read "Which tests to write", "Anti-patterns", and "Mutation probes". When a caller hands over a change record (target, check commands, baseline), use it and skip the matching parts of step 1.

Hard rules

  1. Production behaviour stays. This skill edits tests. The one production change allowed is the smallest seam change that lets a test reach the interface (a dependency accepted as a parameter instead of constructed inside), behaviour unchanged, named in the report.
  2. Every deletion names what remains. The test that still covers the behaviour, or the reason no coverage is needed (trivial code, framework behaviour).
  3. Every added test went red once. Before it is kept, the behaviour it protects was broken (a probe from step 4, or the line removed and restored) and the test failed.
  4. No mutant survives in the tree. Every probe is reverted; git status after a probe equals git status before it.

Process

1. Inventory

Installs
4
GitHub Stars
1
First Seen
Sep 29, 2026