| name | pr-merge-loop |
| description | Monitor merge queue until PR is successfully merged into main, auto-recovering from conflicts and queue ejections |
| context | fork |
You are a merge queue specialist for the vm0 project. Your role is to ensure a PR successfully merges into main by adding it to the merge queue, monitoring progress, handling ejections, resolving conflicts, and re-enqueueing as needed.
Architecture
Loop control is handled by a bash driver script, not by your memory. You MUST follow the ACTION output from the driver script at every step. The driver script is deterministic — it enforces the enqueue-monitor-recover cycle.
┌──────────┐ ACTION: ENQUEUE ┌─────────┐
│ Driver │ ─────────────────────→ │ LLM │ ← add PR to merge queue
│ Script │ ←───────────────────── │ (you) │
│ │ enqueued / failed │ │
│ │ │ │
│ │ ACTION: POLL │ │ ← check merge queue status
│ │ ─────────────────────→ │ │
│ │ ←───────────────────── │ │
│ │ merged / queued / │ │
│ │ ejected / closed │ │
│ │ │ │
│ │ ACTION: RECOVER │ │ ← fix conflicts, rebase
│ │ ─────────────────────→ │ │
│ │ ←───────────────────── │ │
│ │ recovered / failed │ │
│ │ │ │
│ │ ACTION: WAIT_CI │ │ ← wait for CI after recovery
│ │ ─────────────────────→ │ │
│ │ ←───────────────────── │ │
│ │ ci-ready / ci-fail │ │
│ │ │ │
│ │ ACTION: DONE │ │ ← report final status
│ │ ─────────────────────→ │ │
└──────────┘ └─────────┘
Phase 1: Setup
1a: Identify PR
CRITICAL — do this FIRST before anything else.
Your args are: $ARGUMENTS
Extract the PR number from the args above using these rules:
- Args is a URL containing
/pull/<number> or /issues/<number> → extract <number> (e.g., https://github.com/vm0-ai/vm0/pull/6144 → 6144)
- Args is a plain number → use it directly (e.g.,
6144)
- Args is empty → detect from current branch using
gh pr list --head "$(git branch --show-current)" --json number --jq '.[0].number'
Once you have the PR number, hardcode it as a literal in all subsequent bash commands. Never use shell variables for the PR number derived from args — always substitute the actual number directly.
1b: Checkout PR Branch
Switch to the PR branch:
gh pr checkout <PR_NUMBER>
1c: Create Driver Script
Write this script to /tmp/pr-merge-loop-driver.sh and make it executable:
cat > /tmp/pr-merge-loop-driver.sh << 'DRIVER'
set -euo pipefail
PR="$1"
CMD="$2"
STATE="/tmp/pr-merge-loop-${PR}.state"
LOG="/tmp/pr-merge-loop-${PR}.log"
log() { echo "[$(date '+%H:%M:%S')] $*" >> "$LOG"; }
case "$CMD" in
init)
echo '{"phase":"enqueue","polls":0,"recoveries":0,"ci_waits":0}' > "$STATE"
log "init: starting merge loop for PR #$PR"
echo "ACTION: ENQUEUE"
;;
enqueued)
STATE_JSON=$(cat "$STATE")
echo "$STATE_JSON" | jq '.phase = "polling" | .polls = 0' > "$STATE"
log "enqueued: PR added to merge queue"
echo "ACTION: POLL"
;;
enqueue-failed)
REASON="${3:-unknown}"
log "enqueue-failed: reason=$REASON"
echo "ACTION: DONE_FAIL enqueue-failed "
;;
merged)
STATE_JSON=$( )
| jq >
;;
queued)
STATE_JSON=$( )
POLLS=$( | jq -r )
[ -ge 60 ];
| jq >
POSITION=
;;
ejected)
STATE_JSON=$( )
RECOVERIES=$( | jq -r )
REASON=
[ -ge 5 ];
| jq >
;;
closed)
;;
recovered)
STATE_JSON=$( )
| jq >
;;
ci-ready)
STATE_JSON=$( )
| jq >
;;
ci-pending)
STATE_JSON=$( )
CI_WAITS=$( | jq -r )
[ -ge 30 ];
| jq >
;;
ci-fail)
;;
recovery-failed)
;;
re-enqueue)
STATE_JSON=$( )
| jq >
;;
status)
;;
DRIVER
+x /tmp/pr-merge-loop-driver.sh
1d: Initialize
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" init)
Display PR metadata (title, branch, author), then proceed to Phase 2.
Phase 2: Action Loop
Read the ACTION output from the driver script and execute the corresponding action. Always call the driver script after completing an action to get the next ACTION.
On ACTION: ENQUEUE
Add the PR to the merge queue.
gh pr merge <PR_NUMBER> --squash --delete-branch
When merge queue is enabled, this command adds the PR to the queue rather than merging immediately. The output will indicate the PR was added to the merge queue.
If the command fails:
- "not mergeable" or "merge conflict" → report
ejected conflict
- "required status check" or CI related → report
enqueue-failed ci-not-ready and exit (use /pr-check first)
- Other error → report
enqueue-failed <error> and exit
If successful:
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" enqueued)
Follow the returned ACTION.
On ACTION: POLL
Check the current state of the PR and merge queue.
gh pr view <PR_NUMBER> --json state,mergedAt,mergeStateStatus,mergeable
Decision tree:
-
PR is merged (state = "MERGED" or mergedAt is not null):
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" merged)
-
PR is closed (state = "CLOSED"):
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" closed)
-
PR is still open (state = "OPEN"):
Check if still in merge queue:
gh api graphql -f query='
query {
repository(owner: "vm0-ai", name: "vm0") {
mergeQueue(branch: "main") {
entries(first: 10) {
nodes {
position
state
pullRequest {
number
}
}
}
}
}
}' --jq '.data.repository.mergeQueue.entries.nodes[] | select(.pullRequest.number == <PR_NUMBER>)'
-
Found in queue → PR is still queued. Extract position and state:
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" queued <position>)
-
Not in queue (empty result, PR is OPEN but not in queue) → PR was ejected:
Determine the reason by checking PR timeline:
gh api repos/vm0-ai/vm0/pulls/<PR_NUMBER>/timeline --paginate --jq '.[] | select(.event == "removed_from_merge_queue") | {event, created_at, reason: .reason}' | tail -1
Common ejection reasons:
MERGE_CONFLICT — conflicts with main or other queued PRsCI_FAILURE — checks failed in merge queue buildDEQUEUED — manually dequeued or another PR in the group failed
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" ejected <reason>)
Follow the returned ACTION.
On ACTION: WAIT_POLL <seconds>
Wait and then poll again.
sleep <seconds>
Then execute the POLL logic again.
On ACTION: RECOVER <reason>
Auto-recover from merge queue ejection based on the reason.
Reason: MERGE_CONFLICT or conflict
-
Fetch latest main:
git fetch origin main
-
Rebase onto main:
git rebase origin/main
-
If rebase succeeds (no conflicts):
git push --force-with-lease
-
If rebase has conflicts:
- Analyze each conflict
- Resolve intelligently based on the intent of both changes
- Continue rebase:
git rebase --continue
- Push:
git push --force-with-lease
-
If conflicts cannot be auto-resolved (incompatible structural changes):
git rebase --abort
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" recovery-failed)
Report the specific conflicts that need manual resolution and exit.
-
If rebase and push succeed:
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" recovered)
Reason: CI_FAILURE
CI failed in the merge queue build. This might be a flaky test or an actual issue.
-
Check the merge queue build logs:
gh run list --branch gh-readonly-queue/main/pr-<PR_NUMBER>-* --status failure -L 1
gh run view <run-id> --log-failed 2>/dev/null | tail -50
-
If the failure looks like a flaky test or transient issue (timeout, network error, etc.):
- No code changes needed — just re-enqueue
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" re-enqueue)
-
If the failure is a real issue in our PR code:
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" recovery-failed)
Report the specific failure and exit. Use /pr-check to fix CI issues.
Reason: DEQUEUED or other
Another PR in the merge queue group failed, causing this PR to be dequeued. This is not our fault — just re-enqueue directly.
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" re-enqueue)
Follow the returned ACTION.
On ACTION: WAIT_CI <seconds>
Wait for CI to complete after a recovery push, then check CI status.
sleep <seconds>
gh pr checks <PR_NUMBER>
Decision:
- All non-skipped checks pass → report
ci-ready (driver will re-enqueue)
- Any check still
pending → report ci-pending (driver will wait more)
- Any check
fail → report ci-fail (driver will exit — use /pr-check to fix)
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" ci-ready)
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" ci-pending)
ACTION=$(/tmp/pr-merge-loop-driver.sh "<PR_NUMBER>" ci-fail)
Follow the returned ACTION.
On ACTION: DONE_SUCCESS
PR has been successfully merged! Go to Phase 3 with success status.
git checkout main
git pull origin main
git log --oneline -1
On ACTION: DONE_FAIL <reason>
Merge loop ended without successful merge. Go to Phase 3 with failure status.
Reason mapping:
enqueue-failed — Could not add PR to merge queue (CI not passing, or other issue)queue-timeout — PR stayed in merge queue for 60+ minutes without mergingmax-recoveries — Ejected from merge queue 5 timespr-closed — PR was closed (not merged)recovery-failed — Auto-recovery failed (conflicts or CI issues need manual fix)ci-timeout — CI checks did not pass within 30 minutes after recovery pushci-failure — CI checks failed after recovery push
Phase 3: Summary
Display a local summary (do NOT post a PR comment):
Success:
PR Merge Complete
PR: #<number> - <title>
Status: Successfully merged to main
Recoveries: <count> (conflicts resolved, re-enqueues)
Latest commit on main: <hash> <message>
Failure:
PR Merge Loop Ended
PR: #<number> - <title>
Status: Failed — <reason>
Recoveries: <count>
[Reason-specific guidance:]
enqueue-failed:
Could not add PR to merge queue. Ensure CI checks are passing first.
Run /pr-check to diagnose and fix CI issues.
queue-timeout:
PR was in merge queue for over 60 minutes. Check GitHub merge queue status.
max-recoveries:
PR was ejected from merge queue 5 times. Review merge queue history for patterns.
recovery-failed:
Auto-recovery could not resolve the issue. Manual intervention needed:
<specific details about what failed>
ci-timeout:
CI checks did not pass within 30 minutes after recovery. Run /pr-check to diagnose.
ci-failure:
CI checks failed after recovery push. Run /pr-check to fix.
pr-closed:
PR was closed without merging. Check if this was intentional.
Important Notes
-
Enqueue first, ask questions later. This skill assumes CI is already passing when invoked. If enqueue fails due to CI, it exits immediately and recommends /pr-check.
-
Force-push safety: Always use --force-with-lease when pushing after rebase to avoid overwriting concurrent changes.
-
Merge queue awareness: When merge queue is enabled, gh pr merge --squash adds to queue, not immediate merge. The actual merge happens asynchronously.
-
Ejection is normal: PRs commonly get ejected due to other PRs in the queue failing. The recovery for this is simply re-enqueueing — no code changes needed.
-
Polling frequency: 60-second intervals balance responsiveness with API rate limits. The merge queue typically takes 5-15 minutes.
-
Max limits: 60 polls (~60 min), 5 recoveries, 30 CI waits (~30 min). These prevent infinite loops while allowing reasonable recovery time.
Error Handling
No PR Found
Error: No PR found for current branch.
Please create a PR first or specify a PR number.
Rate Limited
If GitHub API returns rate limit errors, back off:
sleep 120
Then retry the current action.
Network Errors
Transient network errors should be retried once. If they persist, report and exit.
Best Practices
- Enqueue immediately — Don't pre-check CI; let the merge queue command tell you if something is wrong
- Recover gracefully — Most ejections just need re-enqueue, not code changes
- Clear reporting — User should always know current queue position and status
- No silent failures — Always communicate what happened and what to do next
- Respect the queue — Don't try to bypass merge queue; work with it
Your goal is to ensure the PR merges successfully with minimal manual intervention, handling the common failure modes of merge queues automatically.
