drive-testlisted

Use when the user says "drive the tests", "/drive-test", "review the tests", "are the tests any good", "check test coverage", or asks Claude to audit test quality across the files a PR (or working tree) touches. Evaluates each touched file's tests for level (unit vs integration vs e2e), assertion quality, mock health, coverage of new code paths, and the classic smells (mocking the unit under test, snapshot churn, tests-that-can't-fail, etc.). Runs the test suite to confirm green, fixes mechanical issues, surfaces judgment calls. Companion to /drive-code (which checks code shape) and /drive-feature (which checks logic).
0xdeafcafe/skills · ★ 0 · Testing & QA · score 75

Install: claude install-skill 0xdeafcafe/skills

# drive-test - audit test quality on touched files drive-test doesn't ask "is there a test"; lots of repos have lots of tests that don't catch bugs. It asks: - Is the test at the **right level**? Unit / integration / e2e. - Does it **actually assert** the behaviour under test? - Does it mock something that **shouldn't be mocked**? - Will it **fail when the behaviour breaks**, and only then? - Is it **independent** - runs alone, in any order, in parallel? Flags missing coverage on **newly added code paths**, runs the suite, applies mechanical fixes, surfaces judgment calls. ## Phase 0 - Scope In priority order: 1. **PR context**: `gh pr diff --name-only` against the base branch. 2. **Working tree**: `git diff --name-only HEAD`. 3. **Explicit list** from the user. For each source file, find its tests (TS/JS `*.test.*` / `*.spec.*`; Python `test_<name>.py` / `<name>_test.py`; Go `<name>_test.go`; Rust inline `#[cfg(test)]`). If no test file exists, flag it for Phase 3. Include test files the PR modifies directly. Exclude snapshots (`__snapshots__/`, `*.snap`), generated scaffolding, `vendor/`, `third_party/`, `node_modules/`, fixtures. ## Phase 1 - Detect the test toolchain Detect runner from config (`vitest.config` / `jest.config` / `playwright.config` / `pytest.ini` / `pyproject.toml[tool.pytest]` / `go.mod` / `Cargo.toml` / `.rspec`). Use the project's `test` script in `package.json` / `Justfile` / `Makefile` - match it instead of guessing flags. ## Phase 2 - Run t