01
What this skill does
Use this skill after a regression-review report or related PR feedback. It verifies every finding, 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
- SignalRe-checking a regression gate against the current diff and baseline.
- SignalFixing only proven user-visible regressions.
- SignalSeparating real regressions from intentional product changes.
03
How it works
- 01
Read the report and list every finding, intentional change, and uncovered surface.
- 02
Verify each item against the current code, baseline, and visible behavior.
- 03
Create a disposition ledger before editing.
- 04
Fix confirmed regressions with narrowly scoped changes.
- 05
Report a disposition for every item and leave Git staging untouched unless asked.
04
What you get back
- SignalA full disposition ledger.
- SignalScoped fixes for confirmed user-visible regressions.
- SignalEvidence for challenged, narrowed, intentional, and carried-forward items.
05
Important boundaries
- SignalDo not blindly apply review feedback.
- SignalDo not stage changes unless the current request explicitly asks for it.
- SignalDo not broaden user-visible behavior while resolving a focused regression finding.
06