# Receiving code review

> Treats review feedback as a technical claim to check: restate it, verify it against the code, then implement it or push back.

Canonical: https://mikereams.com/ai/receiving-code-review

Skill · Curated · Review & QA · updated 2026-10-01. Part of the [AI Library](https://mikereams.com/ai).

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.

- 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.

Source: [obra/superpowers](https://github.com/obra/superpowers/tree/8ca22db/skills/receiving-code-review) by Jesse Vincent (MIT), reviewed at 8ca22db. Not hosted here.

Reviewed 2026-10-01.

Tags: code review, feedback, verification