Borrowing it
Nothing to install: this file belongs to auerbachb/claude-code-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/auerbachb/claude-code-config/main/.claude/skills/babysit-pr/SKILL.mdgit clone --depth 1 https://github.com/auerbachb/claude-code-configWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/auerbachb/claude-code-config/babysit-pr)<a href="https://agentmods.dev/skills/auerbachb/claude-code-config/babysit-pr"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/babysit-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/auerbachb/claude-code-config/babysit-pr"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/babysit-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 934 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00172 | $0.19149 |
| Opus 5.5 | $0.00069 | $0.07660 |
| Sonnet 5.5 | $0.00034 | $0.03830 |
| Haiku 4.5 | $0.00017 | $0.01915 |
Grade A, and why
babysit-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 940 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watch one PR and drive it toward merge without looping forever. Each tick reads the PR's state through the shared scripts, classifies it, and dispatches the right skill — /fixpr to fix recoverable blockers, /wrap to merge when the gate is met — then re-arms the poll until a terminal condition fires.
/babysit-pr is a thin orchestrator: it never re-implements PR-state aggregation, the merge gate, fix logic, or the merge flow. It reads pr-state.sh + merge-gate.sh, and it dispatches /fixpr / /wrap. All code-verification, thread resolution, CI fixing, and merge-gate enforcement stay inside those skills (fixpr/SKILL.md, wrap/SKILL.md, cr-merge-gate.md). This skill only decides which to call and when to stop.
This is reused by /pr-monitor-and-manage (issue #460): that skill invokes /babysit-pr per discovered PR rather than re-implementing the per-PR decision tree.
Safety boundaries (HARD STOPS — non-negotiable, safety.md / #450)
/babysit-pr is read-only plus the dispatches below. It MUST NOT:
- Never babysit a PR you did not author (issue #733,
safety.md). Enrolling a PR in a watch loop is a "touch". Before the first tick, gate the target with"$PR_AUTHORSHIP_SH" <PR>(exit 0 = yours). Not yours / undetermined → refuse with one line naming the authorship guard, and do NOT enrol — unless the user named this specific PR in chat this session (per-PR override; say you are operating under it).polling-state-gate.sh --ensure-sessionalso refuses non-author enrolment as a fail-safe (bypass only with--allow-nonauthorunder that override). - Never modify branch protection — no calls to
.../branches/.../protection. - Never dismiss human-authored reviews. Only
/fixpr'sdismiss-stale-bot-changes.sh(bot allowlist, wrongcommit_id) may dismiss, and only bot reviews. - Never resolve a review thread itself — thread resolution happens only inside
/fixprSteps 1–4 after code-verification./babysit-prdoes not callresolveReviewThread. - Never bypass
/fixpr's code-verification step — it dispatches the full/fixprworkflow, never a shortcut. - Never post
@coderabbitai full reviewwithoutcr-review-hourly.sh --checkpassing first. The only sanctioned trigger path in this skill is the T1b pre-flight (pr-preflight.sh, issue #493), which gates CR oncr-review-hourly.sh(--check+ atomic--record-explicit) automatically, never triggers Greptile, and never flips another user's draft./fixprowns any further triggers after a push.
A human CHANGES_REQUESTED on HEAD is hard-blocked → record and exit. Never auto-dismiss it.
- Auto-resolve mode (
--auto-resolve-conflicts) performs unattended rebases and force-pushes. The resolver (.claude/skills/merge-conflict/resolve_merge_conflicts.py) only applies mechanically-simple hunks per its "when in doubt, complex" contract; any complex hunk aborts the rebase and reports the specific file + line range + reason instead of applying it. Because unattended force-pushes are a bigger authorization step than the rest of the dispatch table, this mode is opt-in — the default onCONFLICTINGis a conservative stop that recommends/merge-conflict.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +78 lines 0b3c75a258d3
- 2mo ago First seen · 862 lines · 172 tokens per session scan A 663bb035c9e1
babysit-pr is a skill published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 2d ago), licensed MIT. It adds 172 tokens to every session and 19,149 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
robin
Use whenever an agent creates, updates, reviews, or completes a GitHub pull request. Detect whether Robin is installed in the repository; when it is, automatically drive the PR through a bounded review, verified-fix, reply, thread-resolution, re-review, authorized-merge, and cleanup loop without requiring the user to…
revert
Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.
upload
Pre-upload gate for track handoff. Verifies review status, HLD approvals, deploy checklist, and validator chain before git upload or PR submission.
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.
kodus-business-rules-validation
Use when the user wants Kodus to validate local diff changes against task requirements, acceptance criteria, or business rules via kodus pr business-validation, especially for implementation-vs-task or merge readiness checks.
Cross-File Leakage リファクタ後の caller 側残骸検出
A code review check for structural changes such as renamed functions, changed arguments, moved files, or split modules. It searches the rest of the project for callers that still use the old structure.