copilot-pr-autopilot
Copilot left 14 review comments on your PR — half are nits. Hours of fix → reply → resolve → re-request, and each round lands MORE comments. This skill runs loop engineering: auto-triggers Copilot Code Review via GraphQL (no @copilot mention), triages every open thread (Copilot, humans, advanced-security) with a fix / decline / escalate rubric, dispatches parallel fix sub-agents that obey the repo build/test/lint conventions, commits per iteration, replies+resolves citing the pushed SHA, then re-triggers until HEAD is reviewed with zero threads awaiting the agent''s reply (remaining open threa
Profile →npx skills add github/awesome-copilot --skill copilot-pr-autopilot --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Copilot PR Autopilot Drive any GitHub pull request through repeated rounds of Copilot code review until the agent has done its job — every Copilot finding has a reply from the agent (fix-acknowledgement, decline-with-rationale, or explicit escalate-to-user hand-off). Remaining open threads, if any, are deliberate hand-offs to the human merge owner — they're not loop failures. Repository-agnostic — works on any repo that has Copilot Code Review enabled, run from a machine with `gh` CLI installed and authenticated (see Prerequisites). ## When to Use This Skill - The user asks to "request Copilot review" or "run a Copilot review loop" on a PR. - A PR is functionally complete and the user wants a final correctness pass via repeated automated review rounds. - A previous Copilot review on the PR has left open threads that need triage, fixing, replying, and resolving. ## When NOT to Use This Skill - The PR is still under active design — wait until the structure is stable; otherwise findings churn round-over-round. - The user wants human reviewer feedback, not Copilot's. ## Prerequisites - `gh` CLI installed and authenticated against the target repository. - PowerShell on PATH — Windows
- When to Use This Skill
- When NOT to Use This Skill
- Prerequisites
- Permissions: who can run the full loop
- Step-by-Step Workflow
- Gotchas
- Troubleshooting
- References
What does the copilot-pr-autopilot skill do?
Copilot left 14 review comments on your PR — half are nits. Hours of fix → reply → resolve → re-request, and each round lands MORE comments. This skill runs loop engineering: auto-triggers Copilot Code Review via GraphQL (no @copilot mention), triages every open thread (Copilot, humans, advanced-security) with a fix / decline / escalate rubric, dispatches parallel fix sub-agents that obey the repo build/test/lint conventions, commits per iteration, replies+resolves citing the pushed SHA, then re-triggers until HEAD is reviewed with zero threads awaiting the agent''s reply (remaining open threa
How do I install it?
Run `npx skills add github/awesome-copilot --skill copilot-pr-autopilot --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.