copilot-review

Requests, waits for, and settles head-scoped GitHub Copilot pull request reviews.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/fx/skills --skill copilot-review-fx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: copilot-review
Source: https://github.com/fx/skills/tree/main/skills/copilot-review
Command: npx skills add https://github.com/fx/skills --skill copilot-review-fx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? GitHub Copilot does not reliably re-review a pull request after new commits are pushed, and its review-request API returns misleading responses, so teams risk merging code that was never actually reviewed for the current head commit. This Skill enforces a per-head-SHA review gate so a PR is only considered reviewed when Copilot has covered the exact commit being merged. ## Core Features & Use Cases - Head-scoped review waiting: A background script polls the GitHub API until a Copilot review's commit_id matches the PR's current head SHA, with a 900-second budget and machine-readable STATUS output. - Verdict and thread triage: Reads the review's verdict headline, ignores suppressed-comments blocks by default, and routes open threads to the resolve-pr-feedback skill with the Scope Brief intact. - Documented API behavior: Encodes empirically confirmed GitHub API quirks (inert review requests, no GraphQL fallback, fail-closed thread counts) so agents do not rediscover or misread them. - Use Case: After pushing review fixes to a PR, run this skill to re-request Copilot, wait for a review of the new head commit, resolve any open threads, and confirm the merge gate before merging. ## Quick Start Ask the agent to run the copilot-review skill with the PR number and Scope Brief to wait for and settle the Copilot review on the current head commit.

Frequently Asked Questions about copilot-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I wait for a GitHub Copilot review on a pull request?▼

Run the wait-for-copilot-review.sh script in the background with the PR number. It polls the GitHub reviews API for up to 900 seconds until a Copilot review's commit_id matches the PR's current head SHA, then prints a STATUS line.

Why does Copilot not re-review my PR after I push new commits?▼

Copilot does not reliably re-review on new pushes unless a repo ruleset enables it, and that ruleset fires inconsistently. You must re-request the review and re-scope the wait to the new head SHA after every push.

Can I check Copilot review status with the requested_reviewers API field?▼

No. The review request POST returns 200 with an empty requested_reviewers list regardless of outcome, and no GraphQL fallback exists for bot reviewers. The only sound signal is polling the reviews endpoint for a matching commit_id.

Should I act on Copilot suppressed comments in a review?▼

Suppressed comments open no review thread and are ignored by default, since acting on them costs a full re-review cycle per push. Only act on an absolutely dire item such as a real defect, security hole, or data loss risk.

What does STATUS=PENDING from the wait script mean?▼

PENDING means no review of the current head arrived within the time budget; it is neither a failure nor evidence the code is clean. Re-run the wait, and never report the review gate as passed based on PENDING.