01
What this skill does
Use this skill when a change set needs a user-visible behavior gate. It reviews a declared scope, separates intended visible changes from regressions, builds scoped behavior-graph deltas when they clarify affected paths, and writes a report that maps every touched surface to reviewed, intentional, not covered, or not relevant.
02
When to use it
- 01Checking whether refactors or feature work broke user-facing flows.
- 02Auditing loading, error, permission, retry, ordering, export, email, or CLI-output changes.
- 03Tracing changed inputs, guards, transforms, and outputs without building a whole-repo call graph.
- 04Producing a review artifact with severity tied to the strongest unresolved finding.
03
How it works
- 01
Set or infer the review scope and read requirements when available.
- 02
Map touched user-visible surfaces before judging behavior.
- 03
Build scoped behavior graph baselines for graphable user-visible or unknown-impact surfaces.
- 04
Compare current behavior against baseline, intent, and user expectations.
- 05
Write all distinct findings, not only the top few.
- 06
Record intentional visible changes and uncovered surfaces in the coverage ledger.
04
What you get back
- 01A Markdown regression-review report.
- 02A gate recommendation aligned to findings and coverage.
- 03A complete findings index, behavior graph deltas, and coverage ledger.
05
Important boundaries
- 01Do not silently sample a large review scope.
- 02Do not treat implementation ugliness as a regression unless it changes visible behavior.
- 03Use `hack-review` instead when the main concern is brittle implementation structure.
06