babysit
Skill207 starsChanged 4 months agoMITView on GitHub
Watch an open PR/MR until it's green or merged — poll checks, kick stalled CI, rerun flakes, catch late review threads. Use for /babysit, "babysit it to green", "watch it", "keep an eye on CI", or any stay-on-it ask after a PR handoff.
- Commits and pushes
44 other projects use a version of this.
Adopted by
Most recently taken up by
- revisit-studies/studytheir own version, first seen Nov 9, 2026
- Yeachan-Heo/oh-my-claude-sisyphustheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 8, 2026
- nightly-labs/openbottheir own version, first seen Nov 8, 2026
- endqwerty/endstacktheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
Used with
Projects with it also use oh-my-issues, what-the and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
tuliosalustiano27Skilloh-my-issues
Cluster a GitHub issue backlog by root cause into a small set of plan-master issues, redirect children with a standardized comment, and bundle architectural-fix PRs that close clusters atomically. Use when an issue tracker has accumulated dozens of reports that share underlying defects, when asked to triage / consolidate / cluster / dedupe issues, when asked to build a plan series or roadmap from open issues, or when routing a new incoming bug into an existing plan.
Also in 3 projects that use this
tuliosalustiano27Skillwhat-the
What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.
Also in 3 projects that use this
Tsumugii24Skillsplit-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
Also in 4 projects that use this
mukcoSkillprinciples
General software engineering principles — DRY, SOLID, YAGNI, KISS, naming, code smells, and refactoring. Language-agnostic. Use alongside language-specific skills.
Also in 5 projects that use this
PandelisZSkillupdate-cli-config
View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.
Also in 3 projects that use this
32103210Skillmigrate-to-skills
Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.
Also in 3 projects that use this
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- simstudioai/sim★ 30ksame name
- nightly-labs/openbot★ 6.3ksame name
- nubjs/nub★ 4.4ksame name
- deadlock-mod-manager/deadlock-mod-manager★ 584same name
- getlago/lago-front★ 163same name
- revisit-studies/study★ 46same name
- Scino/fstack★ 18same name
- ArangoGutierrez/claude-toolkit★ 4same name
34 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- audit-onlySkill
- cleanSkill
- cprSkill
- draft-tweetSkill
- engraved-figuresSkill
- free-disk-spaceSkill
- list-open-workSkill
- notarize-macSkill
- no-tropesSkill
- perfSkill
- pr-readySkill
- pr-triageSkill
- pr-updateSkill
- researchSkill
- runtime-debugSkill
- stacked-prSkill
- ticket-shipSkill
- triageSkill
- ui-onlySkill
- ui-systemSkill
- visual-verifySkill
- workSkill
The file
Files
Babysit
Stay on the PR after handoff until it's actually done. Being asked to babysit IS the ask to poll — but report state changes only, no heartbeats, no per-poll narration.
Loop
- Snapshot:
gh pr view <N> --json state,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup,autoMergeRequestplusgh pr checks <N>. - Poll inside bounded shell loops (a single
forwithsleep 30–60between iterations), not one message per check. Keep watcher scripts, logs, and state outside disposable worktrees, and use a stable working directory; other sessions may remove a merged PR's worktree while its watcher is running. If a watcher fails, recheck the service directly and resume only the remainder of the original deadline. A failed monitor is not a failed deployment. - React by cause:
- CI never started → kick it:
git commit --allow-empty -m "chore: kick CI" && git push. - Red caused by this branch → fix it (the
pr-readyloop), push, resume watching on the new SHA. - Flake / infra red → rerun the failed jobs; repeat until green. Note the flake in one line with the run link.
- New review threads → handle per
pr-ready(fix or reply, verify resolved via the forge API), resume.
- CI never started → kick it:
- Repeat until done. A push or rerun is progress, not an exit.
Merging
Arm automerge only when the user explicitly asks to merge or enable automerge. "Make CI green", "babysit", and "watch it" authorize checks and repairs, not merging. End at green with threads resolved unless merge authorization is explicit.
CI quirks
gh run rerunrefusing with "already running" → cancel the run first, then rerun.- A cancelled run showing "no checks reported" is pending, not red — wait for it to re-report before calling it either way.
- Rollup gates ("All required checks pass") go red because a leaf did — diagnose the leaf failure, never the gate.
Done when
Re-query the forge — don't trust that a push went green or a rerun stuck. Merged, or every check green with no unresolved threads. Fail closed: any red or open thread means keep watching. Wrap up with the PR/MR link and what the watch consumed — reruns used, kicks, fixes pushed.
Scope
- In: watching an open PR, kicking stalled CI, rerunning flakes, small branch-caused fixes, late review threads.
- Out: opening or refreshing the PR (
pr-update,cpr), full rebase/red-CI overhauls (pr-ready), other people's PRs (pr-triage), merging unasked.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

