github/awesome-copilot / skills/copilot-pr-autopilot
copilot-pr-autopilot
VerifiedCopilot 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).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.6 KB |
| references/01-request-review.md | markdown | 1.4 KB |
| references/02-wait.md | markdown | 1.7 KB |
| references/03-list-threads.md | markdown | 1.7 KB |
| references/04-triage.md | markdown | 8.0 KB |
| references/05-fix.md | markdown | 2.4 KB |
| references/06-build-test.md | markdown | 2.1 KB |
| references/07-commit-push.md | markdown | 712 B |
| references/08-reply-resolve.md | markdown | 3.8 KB |
| references/09-convergence.md | markdown | 10.5 KB |
| references/10-cleanup.md | markdown | 707 B |
| references/api-quirks.md | markdown | 8.4 KB |
| references/orchestration.md | markdown | 6.1 KB |
| scripts/01-request-review.ps1 | script | 13.2 KB |
| scripts/02-check-review-status.ps1 | script | 17.4 KB |
| scripts/03-list-open-threads.ps1 | script | 4.0 KB |
| scripts/08-reply-and-resolve.ps1 | script | 3.3 KB |
| scripts/09-review-round.ps1 | script | 5.5 KB |
| scripts/10-cleanup-outdated.ps1 | script | 17.7 KB |
| scripts/_lib.ps1 | script | 15.5 KB |
| templates/reply-decline.md | markdown | 871 B |
| templates/reply-drift.md | markdown | 317 B |
| templates/reply-fix.md | markdown | 839 B |
| templates/reply-partial.md | markdown | 376 B |
references/03-list-threads.md
View on GitHub# Step 3: List + categorize open threads
Sub-agent type: `explore`; budget: 5 min.
## Inputs
- `PrNumber`.
## Return contract
Table of rows, one per open thread:
```
{ thread_id, file, line, author, author_class, severity, summary }
```
Where `author_class` ∈ `copilot` | `human-or-bot`, derived from the
raw `author.login` (see Gotchas).
## Procedure
Run the listing script:
```pwsh
pwsh ./scripts/03-list-open-threads.ps1 -PrNumber <n>
```
This returns every unresolved review thread from **all reviewers**
(Copilot, humans, `github-advanced-security`, other bots). The script
emits `Path` as `<file>:<line>` when the comment is anchored to a
specific line (e.g. `src/foo.js:42`); when the comment has no line
anchor (file-level / PR-level comments), `Path` is just `<file>` with
no `:<line>` suffix. Callers should split on the last `:` **only when
the suffix parses as an integer**, and treat `Path` as the file alone
otherwise. For each row, classify the `author`:
- `copilot-pull-request-reviewer` or
`copilot-pull-request-reviewer[bot]` → `author_class: copilot`
- everything else → `author_class: human-or-bot`
Pass the classified table to step 4 — the triage rubric depends on it.
## Gotchas
- **The `[bot]` suffix appears on some surfaces.** Match BOTH
`copilot-pull-request-reviewer` AND
`copilot-pull-request-reviewer[bot]` — they're the same actor.
- **Default human / advanced-security threads to `escalate-to-user` in
step 4.** Classification here just flags them; triage applies the
policy. See [04-triage.md](04-triage.md).
- **Unresolved is the source of truth.** Outdated-but-unresolved
threads still show up — that's correct. Don't filter them out;
they're handled like any other open thread in step 8.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |