Respond to Review

Take a teammate's review of your PR, check each comment's claim against the code with a reader who did not write it, let the human decide what happens to each one, hand the fixes to /fix-findings, draft the pushback, and leave a record in the project's sidecar to come back to.

Why this skill exists

On a team, most PRs get a human review after /pre-merge has stamped them. Before this skill, the pack had no route for that review. /pre-merge writes .claude/.review-stamped beside its stamp, the post-review edit lock then refuses implementation edits unless /fix-findings is running, and /fix-findings accepted only findings from a /pre-merge run. A teammate's comment was neither, so the only way to act on it was to delete the lock by hand and fix in the session that wrote the code.