babysit-prs

Drives a set of open GitHub pull requests to landed via auto-merge and merge-queue monitoring.

64|11|Updated May 24, 2026
One-click install
npx skills add https://github.com/AlexanderMattTurner/agent-glovebox --skill babysit-prs-alexandermattturner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: babysit-prs
Source: https://github.com/AlexanderMattTurner/agent-glovebox/tree/main/.claude/skills/babysit-prs
Command: npx skills add https://github.com/AlexanderMattTurner/agent-glovebox --skill babysit-prs-alexandermattturner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping a batch of open pull requests moving toward merge is tedious and error-prone: mergeability states are misleading, auto-merge silently disarms, queue evictions look like withdrawals, and serial CI rounds can outlast a work session. This Skill encodes the operational discipline for watching a set of PRs and driving each one to landed without overstepping consent boundaries. ## Core Features & Use Cases - Watch-set management: Builds an explicit, auditable set of PRs to drive, applies ownership labels, refills the set as members merge, and works it oldest-first. - Correct state reading: Interprets GitHub mergeable_state, auto_merge, merge-queue timeline events, and check runs accurately, avoiding false alarms like stale greens or missing required checks. - Parallel fix dispatch: Dispatches load-capped fleets of worktree-isolated fix agents in a single batch, clusters shared red causes, and routes conflicts to the auto-resolve workflow. - Use Case: You ask the agent to babysit ten open PRs overnight; it reads the whole set's status in one command, dispatches fix agents for every red branch at once, re-arms auto-merge where consent exists, and reports blockers loudly until everything lands. ## Quick Start Ask the agent to babysit PRs #4923, #4931, and #4967 and drive them to green and landed.

Frequently Asked Questions about babysit-prs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor multiple open GitHub pull requests at once?▼

Build an explicit watch set of PRs, read the whole set's status in one command, and dispatch fix agents for all red branches in a single batch. Work the set oldest-first by creation date and rebuild it as members merge.

Why does auto-merge keep turning off on my GitHub PR?▼

GitHub clears auto_merge as a side effect of queue eviction, draft conversion, or a merge that makes the PR conflicting. Check the timeline events: a bot eviction means re-arm once fixed, while a human removal of the approved label is a withdrawal.

What does mergeable_state unknown mean on a GitHub pull request?▼

An unknown or null mergeable_state usually means GitHub has not computed a merge commit, very often because the PR is sitting in the merge queue. Confirm queue state via the timeline before attempting to enable auto-merge or merge.

Should I merge a PR directly or use the merge queue?▼

Use auto-merge and the merge queue almost always, because a direct merge skips the queue's batch build against current main. The narrow exception is a reproduced, minimal fix for a red on main itself, pushed directly under strict conditions.

Why does a green PR still fail in the merge queue?▼

A pull_request check runs against a stale merge snapshot, while the queue build tests the head against current main and may run more tests. Diagnose the eviction from the merge_group run's failing jobs, not the PR head's checks.

When should I not re-arm auto-merge on a pull request?▼

Never re-arm while the eviction cause is still live, when a human manually dequeued the PR, or when the approved label was removed. Also never arm a PR that never had auto-merge without explicit user instruction.