← ClaudeAtlas

tighten-testslisted

Slim a branch's tests without losing a covered line or a proof a requirement needs. Use when asked to slim the tests, tighten, trim or prune them, audit the tests, or when a branch has too many tests. Readability of the source is readable-code's, not this skill's; it asks first whether readable-code has run on the final code and offers to run it. Audits every test the branch adds or changes with a keep, merge or drop verdict the author approves, applies the verdicts without changing a source file, proves the smaller suite no weaker by line coverage and mutation checks, has the changes reviewed and fixed, and hands back with the report skill, offering to file each gap it found as an issue. Commits nothing.
sabind/ponderly · ★ 0 · Code & Development · score 69
Install: claude install-skill sabind/ponderly
# Tighten the tests Cut the tests a branch adds or changes down to the ones that prove something, without losing a covered line, a proof a requirement needs or a test the author wants kept. Measure first, decide with the author, apply the decisions, then prove that the smaller suite is no weaker: coverage line by line against the Baseline, and a Mutation_Check for every dropped, kept and new test. The source is never changed; a defect a test exposes is reported, not fixed, and a missing test is handed back as a Gap, not written here. The author is accountable for the tests and decides every Verdict. What a good test is comes from the `tests` rule; this skill applies it and does not restate it. Paths, if the author gave any: $ARGUMENTS Terms used below: - **Scope** is the files the branch changes against its target branch, uncommitted and untracked work included, narrowed to the paths in the arguments when there are any. - The **Baseline** is what is recorded before any test changes: the full suite's result, the test counts, the covered lines per module and the source state. - The **source state** is `git status --porcelain` and `git diff HEAD`, each over every file of the repository that is not a test file, and the contents of the untracked source files, kept in the Run_Folder. - The **Run_Folder** is a new folder in the session's scratchpad, made with `mktemp -d "<scratchpad>/tighten-tests-run-XXXXXX"` at the start of step 2, one per run, so a folder an earlier run left