What problem does it solve?
This Skill maps existing test coverage to the game's GDD critical paths, detects bugs that were fixed without accompanying regression tests, and prevents coverage drift as new features are added. It helps teams maintain a curated regression manifest so fixes do not silently reoccur and release gates can require trusted coverage.
Core Features & Use Cases
- Audit critical paths by scanning design/gdd systems and matching acceptance criteria to unit and integration tests.
- Validate bug fixes by locating closed bugs in production/qa/bugs and checking for corresponding regression tests, flagging gaps and suggesting test file names.
- Detect coverage drift by comparing recent sprint stories, new systems, and file modification history against the last regression-suite update.
- Generate and maintain a manifest at tests/regression-suite.md with a curated index of high-priority regression tests, quarantined tests, and known gaps; ask for confirmation before writing changes.
- Modes: update (append new entries), audit (full rewrite and coverage scoring), and report (read-only status summary).
Quick Start
Run the regression-suite in update mode to scan closed bugs this sprint, map them to tests, and propose updates to tests/regression-suite.md.