prune-tests
Installation
SKILL.md
Prune every test that guards no behavior.
1. Find what each test depends on
Keep a test only if it depends on the intended behavior: it should change only when that behavior changes, and fail only when it regresses.
If another test already guards the same behavior, prune the copy.
Prune tests that depend on:
The past: it asserts that removed code stays gone. Bringing it back would be a decision, not a regression.
For example:
- A feature was removed, and tests assert it's gone.
- A module was moved, and a test asserts it's absent from its old path.
Nothing: no change to the code can make it fail, so it has no reason of its own to change.