Prune Tests

Each cycle takes one test area (a test directory, or the tests for one module), deletes every test in it that would not catch a real bug a stronger test misses, proves coverage held, and opens one PR. One cycle, one area, one PR.

The goal is a smaller suite that protects behavior, not a large suite that protects coverage numbers. A test stays only when it passes the value gate in tdd's testing best practices. That file is the one source for what a good test is. Read it before the first cycle.

Invoking this skill gives the same authority as sweep, per cycle: a branch and worktree, commits, pushing that branch, and opening and labeling its PR. It does not authorize merging or pushing to the default branch.

Every run finds new ground

Runs repeat on the same repo, and earlier PRs stay open for days. Treat earlier work as sweep does: an open, merged, or declined prune-tests/* PR rules out its files. It never ends the run. Move on to the next area.

The keep rule beats the quota. A test that passes the value gate stays, however short of the target the cycle falls. An area whose tests all earn their place ends with no PR and a report of what was examined. That is a correct result.

Arguments

Parse these before any discovery. On invalid input, stop and report it.