pr-swarm
PR Swarm — Parallel Own-PR-to-Green Loops
Problem
A repository checkout can only have one branch active at a time. A user with N independent, already-open pull requests — disjoint branches, disjoint changed files, no real relationship between them — that each need conflict resolution, review-feedback triage, and CI watching wastes wall-clock time driving them one after another when nothing about them actually depends on each other.
Root cause
git worktree removes the one-checkout constraint: N branches can be checked out simultaneously, each in its own directory, sharing one .git object store. Combined with N independent headless Claude Code sessions (own process, own context window, own token budget — not subagents sharing this session's budget), the PRs can be driven to green concurrently with zero cross-talk.
Reference Files
| File | Contents | Load When |
|---|---|---|
references/launch-mechanics.md |
claude -p flags, detached background launch pattern, watchdog/liveness checks, exit-code capture |
Phase 5 (Launch) |
references/verification-gates.md |
GitHub API correctness pitfalls: stale mergeStateStatus, body-only bot reviews, stale statusCheckRollup entries, review-thread pagination, reacting to the first failing check instead of waiting for the full CI matrix |
Phase 6 (Monitor & Verify) |
references/lane-prompt-template.md |
The literal per-lane task prompt (termination conditions, orientation, conflict resolution, watch loop) | Phase 4 (Lane Prompt) |