01
What this skill does
Use this skill after a code-review report or equivalent PR feedback. It builds a disposition ledger for every finding, approval-affecting question, test gap, and open coverage row before changing code, then fixes only what still applies and preserves evidence for challenged, answered, or carried-forward items.
02
When to use it
- 01Re-checking a code-review report against the current diff and baseline.
- 02Fixing confirmed correctness, security, contract, or test issues.
- 03Answering approval-affecting questions with current evidence.
- 04Closing or carrying forward `Not covered` review areas.
03
How it works
- 01
Read the report and enumerate every finding, question, test gap, and coverage gap.
- 02
Verify each item against the current code, baseline, outputs, tests, and relevant call sites.
- 03
Create a disposition ledger before editing.
- 04
Apply scoped fixes for confirmed items while preserving Git staging.
- 05
Report the final disposition for every item and refresh the review when material behavior or coverage changes.
04
What you get back
- 01A full disposition ledger.
- 02Scoped fixes for confirmed review findings.
- 03Evidence for challenged, narrowed, answered, 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 claim the review is clean until every finding, question, test gap, and coverage row is accounted for.
06