← AI Library
Skill · Curated · Review & QA
Receiving code review
by Jesse Vincent · reviewed by Mike Reams
Treats review feedback as a technical claim to check: restate it, verify it against the code, then implement it or push back.
What you get
Each review comment either implemented and tested, one at a time, or answered with the reason it does not apply here.
- When to use it
- When review feedback arrives, before implementing any of it, above all when a comment is unclear or looks wrong.
- Ask for it like this
- “Here is the review on my PR; check each comment against the code before changing anything.”
- Limits
- No performative agreement, and nothing is implemented while any comment is still unclear.
- Works with
- Run it after Code review with a coverage ledger.
What I changed, and why I run it
- Wording edits only: names, and a note on how replies are posted to GitHub.
- The other half of code review. An agent that agrees with every comment is as little use as a reviewer who approves every change.
- code review
- feedback
- verification
Source
- Author
- Jesse Vincent
- Licence
- MIT
- Reviewed at
- 8ca22db
Reviewed 2026-10-01 Passed after edits: every file read by hand and checked for prompt injection, hidden text, network calls, shell execution and credential reads.
Not hosted here: get it from the author, at the commit I reviewed.
