What does this skill do, and when should you use it?
PR Babysitter monitors a GitHub pull request after creation. It polls review comments, CI checks or workflow runs, and mergeability until the PR is merged, closed, or requires user help. It can diagnose branch-related failures, patch and push appropriate fixes, and retry likely flaky checks up to three times. It continues watching open PRs after they become green so new review feedback is surfaced promptly.
Runs the provided Python watcher in one-shot or continuous mode; reads pull-request, review, CI, workflow, and mergeability state; uses GitHub CLI commands to inspect failed runs, jobs, and logs; surfaces published review feedback; patches local code, commits, and pushes when a safe branch-related fix is appropriate; retries failed checks when the watcher recommends it, up to three times; stops when the PR is merged, closed, or blocked on user help.
- A developer wants continuous CI monitoring after opening a pull request.
- A contributor wants newly published review comments surfaced while waiting for approval.
- A maintainer needs to diagnose a test, compile, lint, typecheck, or snapshot failure connected to the PR branch.
- A developer wants likely transient checks retried when the watcher identifies them as flaky or unrelated to the branch.
How do you install this skill?
- The skill may automatically commit, push branch changes, and rerun failed CI during monitoring; confirm the worktree, target branch, GitHub permissions, and organizational approval requirements first.
- Logs and GitHub API responses may contain code, review comments, or build information; the files do not specify redaction, retention, or access controls for sensitive data.
- Core operation depends on gh, GitHub authentication, and continuous network access, which may be unreliable in mainland-China network environments.
- The script and tests were not executed in this static review, so live API compatibility, recovery behavior, and polling behavior remain unverified.
- Shell / CLI
- Network access
- Local filesystem
Python 3GitHub CLI
Install Codex CLI using a README-supported method, such as curl -fsSL https://chatgpt.com/codex/install.sh | sh on macOS or Linux, powershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex" on Windows, or npm install -g @openai/codex and brew install --cask codex. The skill is bundled at .codex/skills/babysit-pr/SKILL.md; the source does not document a separate installation procedure for this skill.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/openai/codex.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/.codex/skills/babysit-pr" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Monitor the PR for the current branch, watch CI and review comments, and keep polling until it is merged, closed, or blocked.
Ask Codex to monitor or babysit an open GitHub PR, for example: “Monitor the PR for the current branch, watch CI and review comments, and keep polling until it is merged, closed, or blocked.” A PR number or URL may also be supplied. Supported commands include python3 .codex/skills/babysit-pr/scripts/gh_pr_watch.py --pr auto --once, python3 .codex/skills/babysit-pr/scripts/gh_pr_watch.py --pr auto --watch, and, only when indicated by the watcher, python3 .codex/skills/babysit-pr/scripts/gh_pr_watch.py --pr auto --retry-failed-now.
What are this skill's strengths and limitations?
- Covers review comments, CI checks, workflow runs, mergeability, and conflicts in one monitoring loop.
- Distinguishes likely branch-related failures from infrastructure and external-service failures.
- Supports up to three retries for likely flaky failures.
- Keeps watching after a PR becomes green so late review feedback is not missed.
- Requires Python 3, GitHub CLI, network access, and suitable GitHub permissions.
- The source provides no test results, supported-platform matrix, or separate skill installation instructions.
- It does not automatically reply to human-authored review comments without explicit confirmation.
- Permission problems, infrastructure failures, exhausted retries, and ambiguous review requests may require user intervention.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| PR Babysitter this page ✓ OpenAI · Official | 57 · Use with care | ★ 129k | 11d ago | Apache-2.0 |
| PR Babysitter: Watch Pull Requests Until Merge | 47 · Use with care | ★ 101k | 12d ago | Apache-2.0 |
| GitHub PR Comment Handler ✓ OpenAI · Official | 42 · Not recommended | ★ 28k | 4mo ago | — |
| babysit — PR Babysitting Skill | 54 · Use with care | ★ 10k | 11d ago | Apache-2.0 |
| Ship a PR (e2e repo PR delivery workflow) | 59 · Recommended | ★ 10k | 11d ago | Apache-2.0 |
How did FollowSkills review this skill?
The skill explicitly restricts replies to human reviewers, limits thread mutation, requires branch-state checks, avoids destructive Git operations, and caps retries, showing meaningful control of permissions and external effects. It can still commit, push, rerun CI, and process GitHub data automatically without per-action confirmation, sensitive-log/data-flow disclosure, or a clear rollback procedure, so points are deducted.
The script, decision tree, and committed pytest tests cover review prioritization, pending reviews, continuous polling, and failed-job log endpoints, with diagnostic error paths described. However, nothing was executed; coverage is incomplete, and operation depends on gh, authentication, GitHub APIs, and live environment state. Several abnormal paths and termination behaviors are not fully proven, so the static score is capped below 10.
Triggers, PR input forms, watch/once modes, and stop conditions are clearly described for GitHub PR maintenance. The skill nevertheless depends on GitHub CLI, GitHub network access, and English-oriented GitHub workflows; non-GitHub boundaries, Chinese interaction, and mainland-China reachability are not documented, so points are deducted.
The material includes objectives, inputs, commands, workflow guidance, failure classification, review handling, mutation policy, references, and tests. The repository also supplies Apache-2.0 licensing, official provenance, and security policy. The skill lacks independent versioning, changelog, named maintenance responsibility, explicit installation/dependency notes, and fuller troubleshooting, so points are deducted.
The intended outcome is concrete: monitor PR state, surface reviews and CI failures, and conditionally fix or retry them. Source tests demonstrate several key behaviors, but no execution was performed, and real permissions, network, branch state, and review judgment materially affect results. Direct usability evidence is therefore limited and scored conservatively within the static cap.
Source code, reference documents, and committed pytest tests provide auditable evidence for several decision paths. There are no executed results, dedicated CI results for this skill, or independent corroboration, so the static score is capped below 5.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →