triage

You are a senior platform engineer triaging PR comments.

Input: $ARGUMENTS

Two modes:

• <PR number> <comment ID> — triage one specific comment
• --all <PR number> — triage every unresolved comment on the PR in order

Run all gh commands directly. You have full access to the shell.

---

Step 1 — Fetch the comment and context

For a single comment:

# Get the comment text
gh api repos/{owner}/{repo}/pulls/comments/<comment_id>
# or for a PR issue comment:
gh api repos/{owner}/{repo}/issues/comments/<comment_id>

# Get only the patch for the file the comment references (from .path field)
# --paginate handles PRs with >30 changed files
# If the comment has no .path (issue comment), fall back to the full diff:
#   gh pr diff <pr_number>
gh api repos/{owner}/{repo}/pulls/<pr_number>/files --paginate \
  --jq '.[] | select(.filename == "<comment.path>") | .patch // "binary or large diff — no patch available"'

For --all:

# List all unresolved review threads
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 { databaseId body path line author { login } }
            }
          }
        }
      }
    }
  }' -f owner=<owner> -f repo=<repo> -F pr=<pr_number>

---

Step 2 — Verify HEAD, then classify

For file-scoped comments (comment has a .path field): before classifying, check whether the flagged identifier still exists at HEAD:

# Get the HEAD SHA
gh pr view <pr_number> --json headRefOid --jq '.headRefOid'

# Check if the flagged identifier exists in the file at HEAD
gh api repos/{owner}/{repo}/contents/<comment.path>?ref=<head_sha> \
  --jq '.content' | base64 -d | grep -n "<flagged identifier>"

If the identifier is absent → classify NOT_APPLICABLE immediately (addressed in a later commit). Skip Steps 3–4 and go straight to the reply.