01
What this skill does
Use this skill after a hack-review report or equivalent PR feedback. It builds a disposition ledger for every finding, intentional exception, and coverage gap before changing code, then fixes only what still applies and preserves evidence for challenged or narrowed items.
02
When to use it
- 01Verifying that each hack-risk finding still applies to the current diff.
- 02Fixing ownership problems without mechanically deleting necessary guards.
- 03Closing or carrying forward `Not covered` ownership boundaries.
03
How it works
- 01
Read the review report and enumerate every finding, exception, and coverage gap.
- 02
Verify each item against the current code before planning edits.
- 03
Create a disposition ledger: fix, disprove, narrow, confirm, or carry forward.
- 04
Apply scoped fixes while naming affected ownership boundaries and regression risk.
- 05
Report the final disposition for every item without staging unless explicitly asked.
04
What you get back
- 01A disposition ledger for the entire report.
- 02Evidence-backed code changes for confirmed items.
- 03A summary of disproven, narrowed, intentional, and carried-forward items.
05
Important boundaries
- 01Do not execute the report mechanically.
- 02Do not stage changes unless the current request explicitly asks for staging or committing.
- 03Narrow or ask before editing if the fix would broaden behavior or weaken ownership boundaries.
06