address-review

Drive the iterative response loop on a PR you own — fetch every piece of review feedback (automated reviewers like CodeRabbit / gemini-code-assist AND human reviewers), triage it, fix the real issues with one focused commit each, run the repo's pre-flight, push, then post a reply to every thread (inline file:line replies plus a PR-level round summary) — because silence makes bots re-raise the same items and leaves humans unsure you saw them. Wait for the next round and repeat until the PR clears the repo's approval threshold — an approving review, or a score like 5/5 from a scoring bot, read from the PR description block first and then from bot comments and review bodies, and never assumed met when no score is found — halting and escalating instead of churning when the repo's impasse or same-file round caps trip. Reads the repo config for repo slug, default branch, pre-flight commands, and the review.* policy. Where the repo sets createPr.requireIssueForDeferredWork, a reply that defers work must name the issue tracking it. Use whenever the user wants to address, respond to, handle, work through, or iterate on review comments on their PR — "address the review feedback", "respond to the review on PR