← ClaudeAtlas

babysit-prlisted

Autonomously drive an open PR to merge-ready state by triaging Greptile and CodeRabbit review comments, fixing CI failures, handling CodeRabbit rate limits, and looping until checks are green with no unresolved actionable threads. With the --merge flag, also merge the PR(s) once binding merge-queue conditions are met. Use when asked to babysit a PR, shepherd a PR, or keep a PR merge-ready until review/CI cycles complete.
lgtm-hq/ai-skills · ★ 0 · Code & Development · score 69
Install: claude install-skill lgtm-hq/ai-skills
# Babysit PR Drive an open pull request to a merge-ready state. This may run for hours — work autonomously in a loop until done or blocked. ## Invocation Examples: - `/babysit-pr on #1034` - `Babysit PR #1034 until merge-ready` - `Babysit this PR` (resolve from current branch) - `/babysit-pr --merge #124 #125 #126` (shepherd **and** merge, in queue order) One babysitter for many PRs beats one babysitter per PR — they share a single CodeRabbit rate limit, so a single session drains the queue without multiplying review-limit stalls. ## Hard rules 1. **Never approve** the PR. **Never merge unless invoked with `--merge`** — the flag is the explicit authorization to merge; without it, only the human owner merges. 2. **Lint before every commit** — read and follow the `lint` skill (`uv run lintro fmt` then `uv run lintro chk`, zero issues). Do not use `--tools` filtering. 3. **Never push while CI is pending or running** on the PR head. 4. **Minimal diffs** — fix only what the PR scope and valid review/CI feedback require. 5. **Never weaken CI/workflows** just to make checks pass; report instead if that seems necessary. 6. **Never force-push**, amend pushed commits, or rewrite history unless the user explicitly requested it. ## Composed skills - **`lint`** — pre-commit formatting and checks (required gate). - **`commit`** — conventional commits, signed commits, semantic prefixes. - **`gh-fix-ci`** (if available) — inspect failing GitHub Actions checks and logs.