review-copilot-pr

review-copilot-pr

What this skill does

1. Detects the current PR (or uses a user-supplied PR number)
2. Fetches all Copilot review threads via GraphQL
3. Analyses each suggestion: accept or reject with reasoning
4. Prints a decision summary table
5. Implements accepted suggestions (code edit → resolve thread → 👍 reaction)
6. Replies to rejected suggestions with a brief explanation

---

Step 1 — Detect repo and PR number

# Get owner/repo slug
gh repo view --json owner,name --jq '"\(.owner.login)/\(.name)"'

# Auto-detect PR from current branch (if no PR number was given)
gh pr view --json number --jq '.number'

If the user passed a number as an argument (e.g. /review-copilot-pr 42), use that directly. If no PR exists for the current branch, tell the user and stop.

---

Step 2 — Fetch all Copilot review threads via GraphQL

Use the GraphQL API to get review threads with their thread IDs (needed for resolution later). The REST API does not expose thread IDs, so GraphQL is required here.

gh api graphql -f query='
{
  repository(owner: "OWNER", name: "REPO") {
    pullRequest(number: PR_NUMBER) {
      reviewThreads(first: 100) {
        nodes {
          id
          isResolved
          comments(first: 10) {
            nodes {
              databaseId
              body
              author { login }
              path
              line
              originalLine
              outdated
            }
          }
        }
      }
    }
  }
}'

Replace OWNER, REPO, and PR_NUMBER with the values from Step 1.

Filter criteria:

• Keep only threads where comments.nodes[0].author.login contains "copilot" (case-insensitive) — this catches copilot[bot], copilot-pull-request-reviewer[bot], etc.
• Skip threads where isResolved: true (already handled)
• Skip threads where comments.nodes[0].outdated: true (code already changed, suggestion stale)

---

Step 3 — Analyse each suggestion

For each remaining thread:

1. Read the Copilot comment body (the suggestion)
2. Read the affected file using the path field from the comment
3. Locate the relevant line using line or originalLine
4. Look at surrounding context (±20 lines) to understand the code

Decision criteria — accept if:

• The suggestion fixes a real bug, prevents a crash, or removes a security issue
• The suggestion improves type safety or eliminates a any/as cast
• The suggestion follows an established pattern already in the codebase
• The suggestion is a straightforward improvement with no downsides

Decision criteria — reject if:

• The suggestion contradicts an intentional design decision visible in the codebase
• The suggestion would break existing behaviour or type contracts
• The suggestion is purely stylistic and the current style is consistent with the rest of the file
• The affected code has already been updated differently in a later commit
• The comment is a question or observation, not an actionable suggestion

Write down your decision and a 1-sentence reason for each thread before taking any action.

---

Step 4 — Print the decision summary

Print this table to the user before making any changes:

## Copilot Review Summary — PR #<number>

| File | Line | Suggestion (brief) | Decision | Reason |
|------|------|--------------------|----------|--------|
| src/foo.ts | 42 | Add null check before access | ✅ Implement | Prevents NPE on missing optional field |
| src/bar.ts | 17 | Rename `data` to `userData` | ❌ Skip | `data` matches the API response shape by convention |

Do NOT take any actions (edits, API calls) before printing this summary.

---

Step 5 — Implement accepted suggestions

For each accepted thread, do these three things in order:

5a. Edit the file

Apply the code change described in the Copilot comment. Read the file first to understand the exact context, then make the minimal edit that satisfies the suggestion. Do not refactor surrounding code.

5b. Resolve the thread

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

THREAD_NODE_ID is the id field from the GraphQL thread node (base64, e.g. PRT_kwDO...).

5c. Add 👍 reaction to the first comment

gh api -X POST /repos/OWNER/REPO/pulls/comments/COMMENT_DB_ID/reactions \
  -f content=+1

COMMENT_DB_ID is the integer databaseId of the first comment in the thread.

---

Step 6 — Reply to rejected suggestions

For each rejected thread, post a reply explaining why you did not implement it:

gh api -X POST /repos/OWNER/REPO/pulls/PR_NUMBER/comments \
  -f body="Thanks for the suggestion! Skipping this one: <1-sentence reason>." \
  -F in_reply_to_id=COMMENT_DB_ID

COMMENT_DB_ID is the integer databaseId of the first comment in the thread. Keep the reply short and factual — one sentence max.

---

Step 7 — Final output

After all actions are done, print a brief completion message:

Done. Processed N Copilot threads:
- X implemented (code changed, thread resolved, 👍 reacted)
- Y skipped (reply posted with reason)

---

Error handling

• If the GraphQL query returns an empty reviewThreads array or no Copilot threads match, tell the user: "No open Copilot review comments found on PR #."
• If a thread resolve mutation fails (e.g. permissions), note it in the output but continue with the remaining threads — don't abort the whole run.
• If a file referenced in a comment no longer exists, reject that suggestion automatically with reason: "File no longer exists."