Resolve Pr Comment

The comment files use comment IDs (PRRC_...), but we need the thread ID (PRRT_...) to resolve. Query the PR to find it:

gh api graphql -f query='
query($owner: String!, $repo: String!, $pr: Int!) {
  repository(owner: $owner, name: $repo) {
    pullRequest(number: $pr) {
      reviewThreads(first: 100) {
        nodes {
          id
          isResolved
          comments(first: 1) {
            nodes {
              id
            }
          }
        }
      }
    }
  }
}' -f owner="OWNER" -f repo="REPO" -F pr=PR_NUMBER

Find the thread where comments.nodes[0].id matches your comment ID (e.g., PRRC_kwDOOjkBEM6gPPfE). The parent id is the thread ID (e.g., PRRT_kwDOOjkBEM5pQksb).

Step 3: Resolve the Thread

gh api graphql -f query='
mutation {
  resolveReviewThread(input: {threadId: "PRRT_..."}) {
    thread {
      isResolved
    }
  }
}'

One-Liner Pattern

For a known comment ID, you can combine these steps. Example for nebariai/nebari-mvp PR #3264:

# Query threads and find the one containing your comment ID
gh api graphql -f query='
query {
  repository(owner: "nebariai", name: "nebari-mvp") {
    pullRequest(number: 3264) {
      reviewThreads(first: 100) {
        nodes {
          id
          isResolved
          comments(first: 1) {
            nodes {
              id
            }
          }
        }
      }
    }
  }
}'

Then resolve with the thread ID you found:

gh api graphql -f query='
mutation {
  resolveReviewThread(input: {threadId: "PRRT_xxxxx"}) {
    thread {
      isResolved
    }
  }
}'

Important Notes

• Thread vs Comment: Comments (PRRC_) are nested inside threads (PRRT_). You resolve threads, not individual comments.
• Only use after fixing: Don't resolve comments you haven't actually addressed.
• Part of pr-review-comments workflow: This is a helper skill, not standalone. Use it after completing a batch in the pr-review-comments workflow.