test-debtlisted

# test-debt skill ## Purpose Measure execution quality, not just completion. A milestone that closes all its tasks but generates a long tail of fix commits was under-specified. The corrective-commit ratio makes this visible as data so the next roadmap generation can improve. ## When invoked By the `/test-debt` command. Requires: - A git repository with commits since the roadmap was executed - `docs/test-readiness/test-readiness-plan.md` (to read milestone task IDs and start dates) ## The corrective-commit ratio ### Definition For a given milestone M: ``` corrective_ratio(M) = corrective_commits(M) / total_commits(M) ``` Where: - **total_commits(M)** — all commits whose message references a task ID from M (e.g., `T-001`, `T-002a`) or the milestone label (e.g., `M1`, `milestone-1`) - **corrective_commits(M)** — commits in total_commits(M) whose message matches a corrective pattern (see below) ### Corrective commit patterns A commit is corrective if its subject line matches any of: | Pattern | Examples | |---|---| | `fix:` or `bugfix:` prefix | `fix: correct auth middleware import path` | | `fix(T-NNN)` reference | `fix(T-042): teardown was leaving DB rows` | | `revert:` prefix | `revert: revert T-015 — broke smoke layer` | | `chore: retry` / `chore: re-run` | `chore: retry T-008 after infra fix` | | Explicit correction language | commit body contains "corrects T-NNN", "follow-up to T-NNN", "missed in T-NNN" | Match case-insensitively. A commit may match multiple pa