Menu
Use when a PR needs Copilot code review and the full review-fix-rereview cycle should be handled autonomously
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Finish a pull request end-to-end from the canonical/root session: investigate PR health (base freshness, checks, review threads, version bumps, local builds), hand off any needed worktree changes to the worktree session as a fix prompt — never mutating the worktree from this session — merge the PR after explicit confirmation, verify post-merge GitHub/Railway deployment health, and close or update related GitHub and Linear issues. Use when the user says a PR is ready to finish, ship, merge, or close out.
Run the packages/protocol eval harnesses correctly — the live LLM harnesses (bun run eval:matching/hyde/premise/profile/opportunity/clarification, which need OPENROUTER_API_KEY auto-loaded from root .env.test) versus the provider-free CI gate (bun run eval:verify, which strips credentials and never calls a model). Use when asked to "run the evals", verify eval suites, add a new eval harness, update a baseline, or when eval:verify fails on an unlisted directory or a baseline-coverage spec after adding a corpus case.
Ship a change to the Edge-City agentvillage submodule end-to-end and bump the index monorepo's submodule pointer, without initializing the submodule in a worktree. Use after merging a PR in Edge-City/agentvillage (or when the pointer at packages/edge-city/agentvillage is stale) — covers the branch-in-submodule → PR-to-Edge-City → pointer-bump-PR-to-dev flow, the git update-index --cacheinfo 160000 plumbing trick for committing a gitlink from a worktree with an empty submodule dir, and restoring the root submodule to a clean detached checkout.
Ship and flip feature flags consistently across ALL env surfaces in the index monorepo — .env.example (committed, commented docs), root .env.development (gitignored local mirror of Railway dev), Railway dev service variables (Railway MCP), and startup.env.ts registration. Use when adding a new env-gated feature flag, enabling/disabling a flag on dev, or when a flag behaves differently locally vs on Railway. Covers the ship-dark→flip order, railway_set_variables gotchas (snake_case ids, map-shaped variables, auto-redeploy), and why the root-dev-guard warning on .env.development edits is safe to ignore.
Create and operate git worktrees in the index monorepo using the project's `bun run worktree:*` helpers instead of raw git. Use whenever you need an isolated branch checkout to make changes (the canonical root must stay on dev and is read-only for the assistant, enforced by the root-dev-guard extension), or when a worktree is missing env files, node_modules, or git hooks, or when a tool/bash call is blocked for touching the canonical root, or when `git commit`/`git rebase` fails with "gpg: signing failed: Inappropriate ioctl for device" in a non-interactive shell. Covers the dashed-folder / slashed-branch naming convention, why `worktree:setup` is mandatory after creating a worktree, and how to disable GPG signing worktree-locally without touching the user's repo-wide signing config.
Open a dated release branch from dev and create a GitHub pull request into main with a generated changelog from git log and git diff. Use when preparing a dev-to-main release PR or when the user asks to cut/open a release PR.
| name | automating-copilot-reviews |
| description | Use when a PR needs Copilot code review and the full review-fix-rereview cycle should be handled autonomously |
Automate the Copilot review cycle on a PR: request review, wait for completion, handle every comment, re-request, repeat until clean.
REQUIRED: Apply superpowers:receiving-code-review when evaluating each comment. Do NOT bulk-resolve threads without reading and evaluating them first.
digraph copilot_loop {
"Check for existing\nunresolved threads" [shape=box];
"Threads already waiting?" [shape=diamond];
"Request Copilot review" [shape=box];
"Poll for review completion\n(30s interval, 10 min cap)" [shape=box];
"Fetch unresolved threads\n(GraphQL)" [shape=box];
"Unresolved threads?" [shape=diamond];
"Evaluate each thread\n(receiving-code-review)" [shape=box];
"Fix or reply,\nthen resolve each" [shape=box];
"Commit and push fixes" [shape=box];
"Round < 5?" [shape=diamond];
"Done — report summary" [shape=doublecircle];
"Surface remaining to user" [shape=box];
"Check for existing\nunresolved threads" -> "Threads already waiting?";
"Threads already waiting?" -> "Evaluate each thread\n(receiving-code-review)" [label="yes"];
"Threads already waiting?" -> "Request Copilot review" [label="no"];
"Request Copilot review" -> "Poll for review completion\n(30s interval, 10 min cap)";
"Poll for review completion\n(30s interval, 10 min cap)" -> "Fetch unresolved threads\n(GraphQL)";
"Fetch unresolved threads\n(GraphQL)" -> "Unresolved threads?";
"Unresolved threads?" -> "Done — report summary" [label="none"];
"Unresolved threads?" -> "Evaluate each thread\n(receiving-code-review)" [label="yes"];
"Evaluate each thread\n(receiving-code-review)" -> "Fix or reply,\nthen resolve each";
"Fix or reply,\nthen resolve each" -> "Commit and push fixes";
"Commit and push fixes" -> "Round < 5?";
"Round < 5?" -> "Request Copilot review" [label="yes"];
"Round < 5?" -> "Surface remaining to user" [label="no"];
}
The bot login differs between APIs:
| API | Login |
|---|---|
REST (/pulls/{pr}/reviews, /pulls/{pr}/comments) | copilot-pull-request-reviewer[bot] |
GraphQL (author.login in review threads) | copilot-pull-request-reviewer |
Using the wrong login silently returns zero results. Always use the table above.
Request review:
gh pr edit <PR> --add-reviewer @copilot
Poll for completion — compare latest Copilot review timestamp against when you requested:
gh api repos/{owner}/{repo}/pulls/{pr}/reviews \
--jq '[.[] | select(.user.login == "copilot-pull-request-reviewer[bot]")] | sort_by(.submitted_at) | last | .submitted_at'
Fetch unresolved threads:
gh api graphql -f query='{
repository(owner: "{owner}", name: "{repo}") {
pullRequest(number: {pr}) {
reviewThreads(first: 100) {
nodes {
id
isResolved
comments(first: 10) {
nodes { databaseId author { login } body path line }
}
}
}
}
}
}'
Filter: isResolved == false AND first comment author is copilot-pull-request-reviewer.
Reply to a thread (use thread root's databaseId):
gh api repos/{owner}/{repo}/pulls/{pr}/comments/{comment_id}/replies -f body="..."
Resolve a thread:
gh api graphql -f query='mutation { resolveReviewThread(input: {threadId: "{thread_node_id}"}) { thread { isResolved } } }'
Determine PR context: Get {owner}, {repo}, {pr} from current branch (gh pr view --json number,url) or user input.
Check for existing threads first: Fetch unresolved threads (GraphQL). If threads already exist from a prior review, skip to step 6 — don't request a new review when comments are already waiting.
Request review: gh pr edit <PR> --add-reviewer @copilot. Record the current timestamp.
Poll for completion: Every 30 seconds, check the reviews endpoint. When the latest Copilot review has submitted_at newer than your recorded timestamp, proceed. Timeout after 10 minutes — tell the user Copilot hasn't responded.
Fetch unresolved threads: GraphQL query, filter for Copilot-authored and unresolved. If zero → DONE. Report a summary of what was fixed, pushed back on, and how many rounds it took.
Evaluate EACH thread individually: Read the comment body, check the referenced file and line in the codebase, apply the receiving-code-review pattern (verify before implementing, push back if wrong, fix if correct). This is where the actual work happens.
For each thread:
git add the affected file.Push: Commit all fixes and git push.
Loop: Go to step 3. Cap at 5 total rounds.
Re-raised comments: Copilot may re-open resolved topics on re-review. Evaluate fresh — the fix may have introduced something new, or Copilot may be repeating itself. If repeating, reply explaining the prior resolution, resolve, and continue.
Timeout: If Copilot doesn't respond within 10 minutes, stop polling and tell the user. Don't silently retry.
No PR on current branch: If gh pr view fails, ask the user for the PR number. Don't guess.
| Mistake | Fix |
|---|---|
| Bulk-resolve without reading | Evaluate each thread per receiving-code-review first |
| Wrong bot login | See Bot Identity table — REST and GraphQL differ |
| Push after re-requesting review | Push fixes BEFORE re-requesting |
gh pr comment for thread replies | Use pulls/{pr}/comments/{id}/replies — gh pr comment posts top-level comments |
| No round cap | Cap at 5 rounds to prevent infinite loops from re-raised comments |
| Silent polling forever | Timeout at 10 min and surface to user |