babysit-pr

babysit-pr is a skill for Codex from jellydn/my-ai-tools. It costs 29 tokens per session (3,561 once invoked), scanned A, a copy of babysit-pr, MIT.

A GitHub pull request monitor that checks continuous integration (automated build and test checks), review comments, and whether the change can be merged.

In plain words
What is it for?
Use it to watch a pull request until it is merged, closed, or blocked by a problem that cannot be safely resolved automatically.
Why use it?
It keeps watching an open pull request and surfaces failures, feedback, and situations that need human help instead of stopping after one status check.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: reads ~/.codex paths; mentions Codex.

Good fit Use it to watch a pull request until it is merged, closed, or blocked by a problem that cannot be safely resolved automatically.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jellydn/my-ai-tools/babysit-pr
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jellydn/my-ai-tools --skill babysit-pr
Clone the repo
git clone --depth 1 https://github.com/jellydn/my-ai-tools

Made for: Codex.

Wrote 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.

agentmods badge for babysit-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/jellydn/my-ai-tools/babysit-pr/github.svg)](https://agentmods.dev/skills/jellydn/my-ai-tools/babysit-pr)
Your own site
<a href="https://agentmods.dev/skills/jellydn/my-ai-tools/babysit-pr"><img src="https://agentmods.dev/badge/skills/jellydn/my-ai-tools/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.

agentmods 80×15 button for babysit-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/jellydn/my-ai-tools/babysit-pr"><img src="https://agentmods.dev/badge/skills/jellydn/my-ai-tools/babysit-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,561 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.03561
Opus 5.5 $0.00012 $0.01424
Sonnet 5.5 $0.00006 $0.00712
Haiku 4.5 $0.00003 $0.00356

Measured 10d ago against content hash c480c7ca57a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 10d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/gh_pr_watch.py, scripts/test_gh_pr_watch.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

91% identical to babysit-pr — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

configs/amp/plugins/my-ai-tools-skills/skills/babysit-pr/SKILL.md · 229 lines

How it starts

The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PR Babysitter

Objective

Babysit a PR persistently until one of these terminal outcomes occurs:

  • The PR is merged or closed.
  • A situation requires user help (for example CI infrastructure issues, repeated flaky failures after retry budget is exhausted, permission problems, or ambiguity that cannot be resolved safely).
  • Optional handoff milestone: the PR is currently green + mergeable + review-clean. Treat this as a progress state, not a watcher stop, so late-arriving review comments are still surfaced promptly while the PR remains open.

Do not stop merely because a single snapshot returns idle while checks are still pending.

Inputs

Accept any of the following:

  • No PR argument: infer the PR from the current branch (--pr auto)
  • PR number
  • PR URL

Core Workflow

  1. When the user asks to "monitor"/"watch"/"babysit" a PR, start with the watcher's continuous mode (--watch) unless you are intentionally doing a one-shot diagnostic snapshot.
  2. Run the watcher script to snapshot PR/review/CI state (or consume each streamed snapshot from --watch).
  3. Inspect the actions list in the JSON response.
  4. If diagnose_ci_failure is present, inspect failed run logs and classify the failure.
  5. If the failure is likely caused by the current branch, patch code locally, commit, and push. Do not patch random flaky tests, CI infrastructure, dependency outages, runner issues, or other failures that are unrelated to the branch.
  6. If process_review_comment is present, inspect surfaced published review items and decide whether to address them.
  7. If a review item is actionable and correct, patch code locally, commit, push, and then resolve the associated review thread only when allowed by the GitHub state mutation policy below.
  8. Do not post replies to human-authored review comments/threads unless the user explicitly confirms the exact response. If a human review item is non-actionable, already addressed, or not valid, surface the item and recommended response to the user instead of replying on GitHub.
  9. If the failure is likely flaky/unrelated and retry_failed_checks is present, rerun failed jobs with --retry-failed-now.
  10. If both actionable review feedback and retry_failed_checks are present, prioritize review feedback first; a new commit will retrigger CI, so avoid rerunning flaky checks on the old SHA unless you intentionally defer the review change.
  11. On every loop, look for newly surfaced review feedback before acting on CI failures or mergeability state, then verify mergeability / merge-conflict status (for example via gh pr view) alongside CI.
  12. After any push or rerun action, immediately return to step 1 and continue polling on the updated SHA/state.
  13. If you had been using --watch before pausing to patch/commit/push, relaunch --watch yourself in the same turn immediately after the push (do not wait for the user to re-invoke the skill).
  14. Repeat polling until stop_pr_closed appears or a user-help-required blocker is reached. A green + review-clean + mergeable PR is a progress milestone, not a reason to stop the watcher while the PR is still open.
  15. Maintain terminal/session ownership: while babysitting is active, keep consuming watcher output in the same turn; do not leave a detached --watch process running and then end the turn as if monitoring were complete.

Read the full file on GitHub · 229 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 10d ago First seen · 229 lines · 29 tokens per session scan A c480c7ca57a8

Subscribe to this mod's changes

babysit-pr is a skill published in the GitHub repository jellydn/my-ai-tools (123 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 3,561 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to babysit-pr, differing in 23 lines, and is treated as a copy.

Related

Other skills, from other repositories

check

Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.

tw93/Waza · 41 tokens

antfu-create-pr

Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.

antfu/skills · 54 tokens

factory-babysit-pr

Experimental workflow for babysitting one explicitly authorized pull or merge request. Use to monitor its live review state and checks, fix actionable in-scope findings, and apply separate reply, approval, merge, and soak gates.

BuilderIO/skills · 50 tokens

factory-review-prs

Experimental workflow for reviewing configured repositories' pull requests. Use for manual or scheduled PR triage, approval, or merge decisions.

BuilderIO/skills · 30 tokens

comet-github-pr-review

A read-only review process for pull requests in Comet's GitHub repositories. A pull request is a proposed code change; the review checks its current code, related issue, comments, merge status, and automated checks.

rpamis/comet · 69 tokens

pr-description-writer

Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…

mohitagw15856/pm-claude-skills · 80 tokens