AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

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 threads are explicit hand-offs to the human — escalated declines, design tradeoffs). You merge a clean PR; the bot runs it. Trigger phrases: "address copilot comments", "run a copilot review loop", "fix this PR", "iterate on copilot feedback". Repo-agnostic, gh CLI + PowerShell. Full autopilot needs repo Triage/Write; external PR authors get single-iteration mode plus manual re-trigger (UI 🔄 or substantive-commit push).

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read github--copilot-pr-autopilot at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 17

references/02-wait.md

Step 2: Wait for review

Sub-agent type: general-purpose; budget: 20-minute hard cap (one bounded sub-agent, NOT extension-driven).

Skipped when the loop is in single-iteration mode — there's no Copilot review to wait for.

Inputs

From step 1:

  • PrNumber.
  • baseline — the LatestCopilotReview.submittedAt string captured before the trigger fired (empty string if no prior Copilot review).

Return contract

  • 02-check-review-status.ps1 JSON snapshot.
  • recommendation ∈ {ready, give-up-push-commit}.
  • ready iff both LatestCopilotReview.submittedAt > baseline AND ReviewAtHead: true.

Procedure

Poll 02-check-review-status.ps1 approximately every 3 minutes until ready or the 20-minute cap is hit:

pwsh ./scripts/02-check-review-status.ps1 -PrNumber <n>
  • Extract submittedAt and ReviewAtHead from the JSON each tick.
  • Stop and return ready on the first tick that satisfies both conditions vs. the captured baseline.
  • On cap reached without ready, return give-up-push-commit.

Gotchas

  • Don't poll faster than ~3 minutes. There is no progress signal from the API; faster polling only burns budget.
  • give-up-push-commit fallback is parent-driven. When the sub-agent returns this recommendation, the parent pushes a substantive (non-whitespace) commit — auto-assign on synchronize is the most reliable trigger. Then the parent re-enters the loop at step 1 with a fresh baseline.
  • Single bounded run, not extension-driven. Do not request extensions on this step — if 20 min isn't enough, the right move is the give-up-push-commit fallback, not more polling.