babysit-pr
Skill3 starsChanged 5 months agoApache-2.0View on GitHub
Follow a GitHub PR through CI and review to a requested outcome, including as part of takeover.
60 other projects use a version of this.
Adopted by
Most recently taken up by
- lihbr/skillstheir own version, first seen Nov 15, 2026
- lucasalencar/skillstheir own version, first seen Nov 15, 2026
- jameswyse/skillstheir own version, first seen Nov 15, 2026
- mynameistito/skillstheir own version, first seen Nov 15, 2026
- rome-os/rometheir own version, first seen Nov 12, 2026
- scottwater/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use html-communication, why and 2 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.
Solly922Skillhtml-communication
Create self-contained HTML artifacts for plans, architecture maps, comparisons, reports, timelines, diagrams, and technical explainers when visual structure improves understanding. Use for complex or spatial information; do not use for short, linear answers that are clearer in Markdown.
Also in 3 projects that use this
jaydubya818Skillwhy
Use when design rationale must be recovered from source history and available records.
Also in 6 projects that use this
jaydubya818Skillhow
Use for runtime, ownership, layering, code-walkthrough, and placement questions.
Also in 4 projects that use this
Hugging FaceSkillsimplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
Also in 5 projects that use this
Other versions60 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 60
- BuilderIO/agent-native★ 7.7ksame name
- camunda/camunda★ 4.4ksame name
- t3dotgg/tstack★ 3.8ksame name
- UniClipboard/UniClipboard★ 2ksame name
- rome-os/rome★ 904same name
- trailofbits/coop★ 816same name
- Mr-Quin/danmaku-anywhere★ 550same name
- tariknz/irdashies★ 270same name
- amElnagdy/review-skills★ 170same name
- owid/etl★ 163same name
50 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 repository44 other files it gives its agents.
- skills/supabase-postgres-best-practices/AGENTS.mdAGENTS.md
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- skills/supabase-postgres-best-practices/CLAUDE.mdCLAUDE.md
- ai-app-security-auditSkill
- ai-slide-templatesSkill
- backlog-ready-specSkill
- check-compiler-errorsSkill
- clawpackerSkill
- councilSkill
- deslopSkill
- devex-reviewSkill
- file-prSkill
- fix-ciSkill
- fix-merge-conflictsSkill
- founder-office-hoursSkill
- full-sendSkill
- full-stopSkill
- get-cookiesSkill
- get-pr-commentsSkill
- gh-issue-priority-handoffSkill
- image2-with-codexSkill
- investigateSkill
- leaving-pr-commentsSkill
- local-ultra-reviewSkill
- modernizeSkill
- npm-release-pipelineSkill
- peer-reviewSkill
- plan-devex-reviewSkill
- planmode-ceoSkill
- planmode-engineerSkill
- qa-onlySkill
- review-and-shipSkill
- run-smoke-testsSkill
- security-best-practicesSkill
- site-design-auditSkill
- site-design-fixSkill
- slow-is-fastSkill
- sol-loopSkill
- supabase-postgres-best-practicesSkill
- takeoverSkill
- vercel-react-best-practicesSkill
- xianyu-api-client-skillSkill
- xianyu-automation-skillSkill
- xianyu-product-manager-skillSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 59 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use when following an existing PR is part of the user's request.
- Distinctive: line 17
Follow CodeRabbit as the primary automated reviewer where used.
- Very specific: line 21
Verify each actionable finding against the current code.
- Very specific: line 25
Follow the PR in the current task using one watcher.
- Distinctive: line 29
Stop when the requested outcome is reached, the PR closes, or a decision outside the granted scope is needed.
“Common” is measured: kept by at least 6 in 10 of the 59 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
Babysit PR
Use when following an existing PR is part of the user's request. Default to following through required checks and review, then report any remaining approval. Fix, push, post replies, resolve threads, or merge within the user's authorization for those actions.
- Resolve the live PR, head SHA, and base. Read existing checks and review
feedback before waiting. Use
gh pr viewfor review and merge state andgh pr checksfor PR checks. Use--requiredfor reported required checks and verify the repository rules if an expected check is missing. - Follow CodeRabbit as the primary automated reviewer where used. Include QA, human reviews, and other bots as configured or requested. Use the repository rules and the user's request to determine what must finish. Keep optional results separate and distinguish pending, failed, and completed reviews.
- Verify each actionable finding against the current code. Focus authorized
fixes on real issues, test before pushing, and use
leaving-pr-commentsfor any authorized reply. Preserve the context of existing review threads. - Follow the PR in the current task using one watcher. For reported pending
required checks, use
gh pr checks --required --watch --fail-fast. Refresh the live PR periodically when waiting for review. Re-read reviews and checks after each push and whenever the head or relevant base changes. - Stop when the requested outcome is reached, the PR closes, or a decision outside the granted scope is needed. Report CI, review, and any remaining approval separately. Check GitHub's live review decision and merge state before saying a PR is ready.
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.

