01
What this skill does
Use this skill after a regression-review report or related PR feedback. It verifies every finding, behavior graph delta, intentional visible change, and coverage gap against the current code before editing, then fixes proven regressions and challenges stale or intentional findings with evidence.
02
When to use it
- 01Re-checking a regression gate against the current diff and baseline.
- 02Reconciling behavior graph deltas with findings and coverage rows.
- 03Fixing only proven user-visible regressions.
- 04Separating real regressions from intentional product changes.
03
How it works
- 01
Read the report and list every finding, intentional change, and uncovered surface.
- 02
Reconcile behavior graph deltas with the current code path and coverage ledger.
- 03
Verify each item against the current code, baseline, and visible behavior.
- 04
Create a disposition ledger before editing.
- 05
Fix confirmed regressions with narrowly scoped changes.
- 06
Report a disposition for every item and leave Git staging untouched unless asked.
04
What you get back
- 01A full disposition ledger.
- 02Scoped fixes for confirmed user-visible regressions.
- 03Evidence for challenged, narrowed, intentional, and carried-forward items.
05
Important boundaries
- 01Do not blindly apply review feedback.
- 02Do not stage changes unless the current request explicitly asks for it.
- 03Do not broaden user-visible behavior while resolving a focused regression finding.
06