babysit

Monitors a pull request until checks and reviews pass, then runs configured merge and cleanup closeout.

10|Updated May 12, 2026
One-click install
npx skills add https://github.com/sandsower/beislid --skill babysit-sandsower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: babysit
Source: https://github.com/sandsower/beislid/tree/main/skills/babysit
Command: npx skills add https://github.com/sandsower/beislid --skill babysit-sandsower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a pull request green requires repeatedly polling CI, triaging review feedback, re-running quality gates, and then remembering to merge, close the ticket, and delete the branch. This Skill automates that outer-loop supervision so a PR reaches a verified green state and a policy-controlled closeout without manual babysitting. ## Core Features & Use Cases - Live PR monitoring: Reads checks, mergeability, review decisions, and inline review threads from the configured PR host, and treats skipped or rate-limited reviewer bots as not reviewed even when their status is green. - Feedback and gate handling: Delegates review feedback to the review-response workflow and runs configured quality gates before any push or merge preparation. - Configurable closeout: Supports off/ask/auto modes for merge, knowledge capture, retro, and cleanup, including ticket closing and remote branch deletion after a verified merge. - Use Case: After opening a PR, ask the agent to babysit it; it waits for CI, addresses review comments, verifies nothing is unlanded, merges with squash, closes the linked ticket, and deletes the remote branch. ## Quick Start Ask the agent to babysit the current pull request until it is green and then merge it according to the configured closeout policy.

Frequently Asked Questions about babysit

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

FAQPage Schema
How do I automatically monitor a pull request until CI passes?▼

Run the babysit workflow on the current branch's PR. It polls checks, mergeability, and review threads at bounded intervals, handles feedback through review-response, and stops with evidence once the PR is green or blocked.

How do I auto-merge a GitHub PR after reviews are resolved?▼

Set closeout merge mode to ask or auto in the workflow config. After a green audit passes, babysit merges with the configured method such as squash, subject to action policy approval, and can then close the ticket and delete the remote branch.

Does babysit work without Claude Code or Pi persistence features?▼

Yes, persistence is optional. Without it, babysit performs the current audit, feedback, and gate step, then stops with evidence and the next recheck action if the PR is not yet terminal green.

Why does babysit say a PR is not reviewed when the review bot check is green?▼

A green reviewer status is not trusted alone. Comments indicating review skipped, rate limited, limit reached, or draft detected are treated as deferred review, so the green audit fails until a real review exists.

Will babysit delete my local branch or worktree during cleanup?▼

No. Cleanup never removes the worktree or local branch; it only reports them as ready for removal by the supervising session. It also stops if any branch content has not landed on the default branch.