babysit
Skill4 starsChanged 2 months agoMITView on GitHub
Babysit a pull request to approval: watch CI and the automated reviewers, action or push back on each comment, push fixes, keep watching until the bots have nothing left to say. Use when the user asks to babysit, monitor, or watch a PR, or to take one through review until it is mergeable.
47 other projects use a version of this.
Adopted by
Most recently taken up by
- laceyp99/skillstheir own version, first seen Nov 16, 2026
- mlschodkowski/skillstheir own version, first seen Nov 16, 2026
- Expensify/Apptheir own version, first seen Nov 15, 2026
- nightly-labs/openbottheir own version, first seen Nov 14, 2026
- revisit-studies/studytheir own version, first seen Nov 9, 2026
- Yeachan-Heo/oh-my-claude-sisyphustheir 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 versions47 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 47
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- simstudioai/sim★ 30ksame name
- nightly-labs/openbot★ 7.9ksame name
- Expensify/App★ 5.1ksame name
- nubjs/nub★ 4.4ksame name
- deadlock-mod-manager/deadlock-mod-manager★ 584same name
- OutThisLife/brooklyn-skills★ 215same name
- getlago/lago-front★ 163same name
- revisit-studies/study★ 46same name
37 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-voiceSkill
- changelogSkill
- commitSkill
- desert-modeSkill
- dispatchSkill
- handbackSkill
- handoffSkill
- mailboxSkill
- open-prSkill
- quickchartSkill
- reviewSkill
- session-usageSkill
- spawnSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
If there is no PR yet, open one with open-pr.
- Distinctive: line 30
Triage: every new comment (below).
- Distinctive: line 42
Every comment gets a decision, and the decision is yours — a bot's comment is an argument, not an instruction.
- Distinctive: line 45
Action it: when it names a real defect, a repo convention the change misses, or a case the tests do not cover.
- Distinctive: line 51
When a comment turns on a judgement the operator owns — a product decision, a deliberate trade-off, an architectural direction — stop and …
- Distinctive: line 64
Stop early and say so when the loop stops converging: the same comment surviving two rounds of fixes, CI failing for a reason outside the …
“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Babysitting is a loop, not a single pass — each push provokes another round of CI and reviewer comments.
The loop
Resolve the PR first: a number or URL the operator gave, otherwise the PR for
the current branch (gh pr view --json number,url,state,statusCheckRollup,reviews).
If there is no PR yet, open one with open-pr.
Then, until done:
- Wait for the PR to change — CI settling, a reviewer posting.
gh pr checks --watchblocks on CI; read the review threads between rounds rather than spinning tightly. Bots are slow, and a quiet PR is usually a pending one, not a finished one. - Triage every new comment (below). Red CI is a comment too — read the failing log and treat the cause as an action item.
- Fix what you agreed with, through
tdd: the failing test first, then the change. - Reply to what you disagreed with, on the review comment itself, with the reasoning that changed your mind about it.
- Push, and go back to 1. A push restarts CI and re-triggers the reviewers; expect another round, and expect the round after that to be smaller.
Triage
Every comment gets a decision, and the decision is yours — a bot's comment is an argument, not an instruction.
Action it when it names a real defect, a repo convention the change misses, or a case the tests do not cover. Push back when the bot has missed context the diff does not carry, is restating a choice made deliberately, or is asking for scope the issue did not ask for; say which, in a reply, so the thread carries the reasoning rather than silence.
When a comment turns on a judgement the operator owns — a product decision, a deliberate trade-off, an architectural direction — stop and ask them. Guessing on their behalf is how a babysat PR drifts away from what they wanted.
Done
Done is all three at once: CI green, every comment either fixed or answered, and every automated reviewer approving.
Then stop and hand the PR back — its URL, what you changed in response to review, and what you pushed back on. Merging is the operator's, in that moment or a later prompt; babysitting ends at approved.
Stop early and say so when the loop stops converging: the same comment surviving two rounds of fixes, CI failing for a reason outside the diff, or a reviewer that never posts. A stalled loop reported is worth more than a loop still running.
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.

