What problem does it solve?
This skill standardizes post-change regression assessment to prevent narrow fixes or bugfixes from breaking adjacent behavior, hiding side effects, or degrading repository health without explicit tracking.
Core Features & Use Cases
- Evidence-driven assessment: maps changed surface to likely regression zones and aggregates verification evidence such as diffs, changed tests, smoke, and full verification reports.
- Policy-aware gating: classifies residual risk against configured thresholds and influences approval outcomes by setting approve/pending/reject actions and follow-up tasks.
- Artifact updates and traceability: records findings in session summary, known issues, current task, and backlog when follow-up work is required.
- Use Case: a reviewer validating a bugfix or feature that touched shared runtime or API contracts and needing a narrow, reproducible regression verdict.
Quick Start
Use the regression-check skill to analyze the recent change, run focused verification for adjacent areas, classify residual regression risk, and record findings in the session summary.