Menu
Babysit open PRs — auto-rebase, fix CI, address review comments. Use with /loop 5m /babysit for hands-free PR management.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | babysit |
| description | Babysit open PRs — auto-rebase, fix CI, address review comments. Use with /loop 5m /babysit for hands-free PR management. |
| model | opus |
Check all open PRs in this repo and shepherd them toward merge:
List open PRs: gh pr list --state open --json number,title,headRefName,statusCheckRollup,reviewDecision
For each PR, check in order:
a. CI status: If checks are failing, read the failure logs (gh pr checks <number>), diagnose, and fix in the PR's branch worktree.
b. Merge conflicts: If the PR has conflicts with master, rebase it:
git worktree add .claude/worktrees/rebase-<number> <branch>
cd .claude/worktrees/rebase-<number>
git rebase master
git push --force-with-lease
c. Review comments: If there are unresolved review comments (gh api repos/{owner}/{repo}/pulls/<number>/comments), address them in a worktree and push.
d. Stale: If the PR is >7 days old with no activity, report it.
Report a summary table:
| PR | Branch | CI | Conflicts | Reviews | Action Taken |
|---|
Do NOT merge any PR. Only fix CI, rebase, and address comments. Merging requires explicit approval.
Break an issue into tasks so small and precise that each has exactly one correct implementation. Refuses to launch execution until the plan contains actual code shapes, verified file paths, and scope locks. Use before any implementation session.
Use when implementing a milestone with multiple issues. Thesis-first approach: write failing E2E tests before issues, expert-review acceptance criteria before implementation, use dedicated terminal sessions (not subagents), and verify E2E yourself before merging. Includes review cycle that creates follow-up issues when expert review surfaces new gaps.
Use when the user wants to find, catalog, or address technical debt. Also use when starting a cleanup sprint, looking for code quality improvements, or asking "what needs cleaning up?"
Run Holzmann "Power of Ten" discipline review on changed code. Checks nesting depth, loop bounds, function size, preconditions, mutable state, side effect surfacing, and indirection depth. Use after writing code, before committing, or as part of PR review. Outputs a weighted letter grade (A-F) with stoplight color.
Use when completing a feature, before creating a PR, or when the user asks "what do my experts think?" Dispatches the expert panel as parallel subagents for structured code review from multiple perspectives.
Commit staged changes, push branch, and create a PR with full pre-flight verification.