regression-managerlisted
Install: claude install-skill YevheniiaQA/qa-agent-toolkit
# Regression Manager
Everything upstream produces tests. This skill is about what happens to them
afterwards — which is where most suites quietly die, not from being badly written
but from never being maintained.
## Verifying a fix
When a defect is reported fixed, the test that proved it already exists and is
marked as an expected failure. Do not write a new one.
1. **Run the existing test.** A strict expected failure reports "expected to fail,
but passed" when the defect is resolved. That message is the verification.
2. **Confirm the pass is for the right reason.** Probe directly, outside the
suite, exactly as the debugging stage does. An expected failure can flip to
passing because the environment broke in a way that happens to satisfy the
assertion — this has happened before and will happen again.
3. **Remove the marker**, keep the test, and record the defect ID and the date in
a comment. The test now guards the fix.
4. **Check for adjacent regressions.** A validation fix frequently breaks the
happy path. Run the whole requirement's scenarios, not just the one test.
5. **Update the traceability**: requirement moves from `Covered (failing)` back to
`Covered`; the defect closes with the verifying run referenced.
Never close a defect on a passing test alone without step 2.
## Merging new tests into the regression suite
New tests arrive per ticket. The regression suite is not "all tests ever written"
— that is how a suite reaches four hours and gets