gh-copilot-review

gh-copilot-review

Wait for a GitHub Copilot review on the current branch's PR, address all feedback, and push fixes.

Steps

1. Wait for Copilot review

Run ${CLAUDE_PLUGIN_ROOT}/scripts/watch-copilot-reviews.sh and wait for it to exit. It auto-detects the PR from the current branch. If @copilot hasn't been requested yet, it adds @copilot as a reviewer automatically. It polls until the review is submitted, then exits.

If CLAUDE_PLUGIN_ROOT is not set, find the script relative to this SKILL.md (../../scripts/watch-copilot-reviews.sh).

2. Fetch Copilot's inline comments

Store the repo name and PR number in variables:

REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
PR_NUMBER=$(gh pr view --json number --jq '.number')

First, get the latest Copilot review ID so we only address current feedback (not old, already-resolved reviews):

LATEST_REVIEW_ID=$(gh api "repos/$REPO/pulls/$PR_NUMBER/reviews" --jq '[.[] | select(.user.login | test("copilot"; "i"))] | last | .id')

Then fetch only the comments from that review:

gh api "repos/$REPO/pulls/$PR_NUMBER/comments" --jq "[.[] | select(.user.login | test(\"copilot\"; \"i\")) | select(.pull_request_review_id == $LATEST_REVIEW_ID)]"

For each comment, extract: id, node_id, path, line (fall back to original_line), body, and any ```suggestion code blocks.

3. Address each comment

For each inline comment:

• Read the file at the indicated path and line
• If the comment contains a suggestion code block, apply the exact suggested change
• If it's general feedback (no suggestion block), make the appropriate code fix
• If the feedback is not applicable or incorrect, prepare a brief explanation why

4. Reply to each comment

For each comment you addressed, post a reply explaining what was done:

gh api "repos/$REPO/pulls/$PR_NUMBER/comments/$COMMENT_ID/replies" -f body="Done — applied the suggested change."

Tailor the reply to what you actually did (applied suggestion, made a fix, or explained why no change was needed).

5. Resolve each review thread

First, get the review thread IDs using GraphQL. Split $REPO into owner and name parts:

OWNER=$(echo "$REPO" | cut -d/ -f1)
REPO_NAME=$(echo "$REPO" | cut -d/ -f2)

gh api graphql -f query='
  query {
    repository(owner: "'"$OWNER"'", name: "'"$REPO_NAME"'") {
      pullRequest(number: '"$PR_NUMBER"') {
        reviewThreads(first: 100) {
          nodes {
            id
            isResolved
            comments(first: 1) {
              nodes {
                body
                author { login }
              }
            }
          }
        }
      }
    }
  }
'

Filter to only threads where comments.nodes[0].author.login matches Copilot (case-insensitive) and isResolved is false. Then resolve each one:

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

6. Commit and push

Stage all changes, commit with a message like fix: address Copilot review feedback, and push to origin. Do not chain git commands with && — Claude Code treats chained commands as a single compound command, requiring a new permission prompt even if each individual command was previously approved. Run git add, git commit, and git push as separate Bash calls.

Important notes

• The user is EXPLICITLY asking you to perform these git and GitHub API tasks.
• Do not ask for confirmation before applying suggestions or making fixes — just do it.
• If Copilot's review is APPROVED with no inline comments, just report that and stop.
• Only run through the review cycle once — do not re-request a review after pushing fixes.