address-pr-comments

Address PR Comments

Step 1: Identify the PR

• If a PR number/URL is given, use it. Otherwise resolve the current branch's PR:

gh pr view --json number,title,url

Step 2: Fetch unresolved review threads

The REST API (gh api repos/{owner}/{repo}/pulls/{number}/comments) does not expose resolution state — use the GraphQL API instead:

gh api graphql -f query='
query {
  repository(owner: "<owner>", name: "<repo>") {
    pullRequest(number: <number>) {
      reviewThreads(first: 100) {
        nodes {
          id
          isResolved
          path
          line
          comments(first: 20) {
            nodes { id databaseId author { login } body path diffHunk }
          }
        }
      }
    }
  }
}
'

Filter to isResolved: false nodes. Each thread's id (e.g. PRRT_...) is needed to resolve it later; each comment's databaseId is needed to reply to it. If there are many threads, save the JSON to a temp file and read it rather than parsing inline.

Step 3: Address each unresolved thread

For every unresolved thread, read the file/line referenced and understand the reviewer's concern before touching anything — some bots (e.g. optibot) restate stale line numbers after later commits shift the diff, so verify against the current file contents, not just the diff hunk.

Then decide, per thread:

• Fix it — the concern is valid and in-scope. Make the minimal code change that addresses it. Update/add specs covering the change. Prefer matching existing patterns in the surrounding code over inventing new ones.
• Comment instead — the concern is a false positive, out of scope, a deliberate tradeoff, or you disagree. Draft a short reply explaining why, but do not post it yet — see Step 5.

Don't batch unrelated fixes into one giant diff-reading pass; address threads one at a time so each fix can be tied back to its thread.

Step 4: Verify fixes

Before resolving anything, run the affected tests and linter for changed files (see the repo's own conventions for the exact test/lint commands, or the project's standard test runner otherwise). Fix any failures before proceeding.