regression-suite

# Regression Suite This skill ensures that every bug fix is backed by a test that would have caught the original bug — and that the regression suite stays current as the game evolves. It also detects when new features have been added without corresponding regression coverage. A regression suite is not a new test category — it is a **curated list of tests already in `tests/`** that collectively cover the game's critical paths and known failure points. This skill maintains that list. **Output:** `tests/regression-suite.md` **When to run:** - After fixing a bug (confirm a regression test was written or identify gap) - Before a release gate (`/gate-check polish` requires regression suite exists) - As part of sprint close to detect coverage drift --- ## 1. Parse Arguments **Modes:** - `/regression-suite update` — scan new bug fixes this sprint and check for regression test presence; add new tests to the suite manifest - `/regression-suite audit` — full audit of all GDD critical paths vs. existing test coverage; flag paths with no regression test - `/regression-suite report` — read-only status report (no writes); suitable for sprint reviews - No argument — run `update` if a sprint is active, else `audit` --- ## 2. Load Context ### Step 2a — Load existing regression suite Read `tests/regression-suite.md` if it exists. Extract: - Total registered regression tests - Last updated date - Any tests flagged as `STALE` or `QUARANTINED` If it does not exist: note "No regre...