test-prunelisted

# test-prune Audit and trim a test suite. Finds tests that duplicate other coverage, test stdlib behavior, or only assert that a mock was called. Verifies before removing — a test cannot be declared redundant without showing the other test that covers the same behavior. Run this skill when: - A project has shipped several build phases and the test suite has grown faster than the source tree. - Test runs are slow and a chunk of the slowness is integration tests that re-cover unit-test scenarios. - The user says "prune the tests", "clean up the test suite", or "the integration tests are redundant". This skill does NOT touch application code, README, plan docs, or git state. It edits tests/, runs the test gate, and reports. --- ## Phase 1 — Identify candidates Always dispatch this phase as parallel Explore agents — never as a serial in-line scan, even for small test suites. Launch 1–3 parallel Explore agents (scale agent count to test-file count: 1 agent for ≤5 files, 2 for 6–20, 3 for >20) to read every test file under `tests/` (or the project's test directory) and flag: 1. **Redundant tests** — same behavior tested in multiple files (especially integration tests that duplicate unit tests). 2. **Trivial tests** — testing stdlib behavior (dict keys exist, dataclass defaults, `Path.mkdir()` works). 3. **Mock theater** — tests that only assert a mock was called, with no real logic under test. 4. **Duplicate coverage** — integration file that re-tests every unit-test scenari