Respond to PR Review

Systematically triage, address, and respond to every review comment on a pull request. No comment should be silently skipped.

Core Principle

Every review comment gets an explicit disposition. A comment is either:

1. Accepted — the feedback is valid, fix the code and respond
2. Acknowledged — the feedback is valid but out of scope for this PR; respond explaining why and what follow-up is planned
3. Disputed — the feedback is incorrect or conflicts with project rules; respond with a concrete explanation referencing the relevant invariant or rationale

Never silently skip a comment. Never dismiss a comment just because it is non-blocking, a suggestion, or an improvement rather than a bug. Automated reviewers (Greptile, CodeRabbit) are configured with project-specific rules — their feedback reflects project standards and should be treated with the same rigor as human review comments.

Instructions

1. Determine PR number

If not provided, detect from current branch: