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
SkillScore77Maintained
Automatic
◆Coding pack
Last verified 8/2/2026
What it changes
Passed 15 of 19 test cases with the skill, and 7 of 19 without it.
Without skill36%
With skill77%
Checks it passed that the model alone missed
Requires zero open threads awaiting reply.
Skips the review request trigger and wait steps.
Requires latest review commit SHA to match current HEAD OID.
and 8 more in the full report
9 fixed8 passed either way5 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+205%
Agent turns
0%
Response time
-40%
Model gemini-3.6-flashMeasured 8/2/2026v117 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
During thread triage, a complex thread is assigned the escalate-to-user disposition. Should 08-reply-and-resolve.ps1 be called with or without resolving the thread?
What was checked, without and with the skill
Checked
Without skill
With skill
Posts the analysis reply while keeping the thread unresolved using -NoResolve.
Missed
Passed
case-12 · gemini-3.6-flash · 8/2/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md153 lines24 filesincludes scripts
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 PowerShell 5.1+ (powershell.exe) or
PowerShell 7+ (pwsh). Both are tested.
Copilot Code Review is the primary use case (01-request-review.ps1
uses GraphQL requestReviewsByLogin to trigger Copilot). It is
NOT a hard requirement — if 01-request-review.ps1 fails
because Copilot isn't enabled on the repo / account, the agent can
still drive existing review threads (human, advanced-security, etc.)
to completion by running steps 3–8 once as a single iteration; just
skip the trigger + wait. There is no auto-detect for "Copilot
unavailable" — the agent makes that decision after the trigger
fails (the script can't reliably tell "Copilot disabled" from