babysit-pr
Skill105 starsChanged 26 days agoMITView on GitHub
Drive an open djangofmt PR to green — conflicts, failing CI jobs, review threads, CodSpeed and ecosystem-check verdicts.
65 other projects use a version of this.
Adopted by
Most recently taken up by
- tekumara/skillstheir own version, first seen Nov 16, 2026
- zanellig/skillstheir own version, first seen Nov 16, 2026
- arraydude/agent-skillstheir own version, first seen Nov 16, 2026
- rodeyseijkens/skillstheir own version, first seen Nov 16, 2026
- tunnckoCore/skillstheir own version, first seen Nov 16, 2026
- gmunaro/claude-skillstheir own version, first seen Nov 16, 2026
Used with
Projects with it also use leaving-pr-comments, sol-loop 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.
cogine-aiSkillleaving-pr-comments
Use whenever leaving comments on GitHub.
Also in 12 projects that use this
tekumaraSkillsol-loop
Use when the user says "sol loop".
Also in 10 projects that use this
tunnckoCoreSkillfull-stop
Trigger this if the user says 'full stop', even as a closing "Full stop." that reads like emphasis.
Also in 13 projects that use this
cogine-aiSkillmodernize
For getting old prs up to date. Use when asked to rebase a pr or "modernize".
Also in 10 projects that use this
tekumaraSkillfile-pr
Raise a concise pull request. Use when the user asks to raise, open, or create a PR.
Also in 17 projects that use this
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
- +1 more from tekumara
- +1 more from cogine-ai
Other versions65 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 65
- 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★ 551same name
- tariknz/irdashies★ 272same name
- amElnagdy/review-skills★ 170same name
- owid/etl★ 166same name
55 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 repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-lint-ruleSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 63 edited versions we read keep these.
0
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 14
CodSpeed: follow codspeed:codspeed-optimize.
“Common” is measured: kept by at least 6 in 10 of the 63 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
Takes a PR number; default is the current branch's PR. Fix everything locally, then push once: CodSpeed is slow.
- Conflicts: rebase on
mainonly when the PR isCONFLICTING. Done when it'sMERGEABLE. - Failing CI jobs: reproduce each with its
justrecipe. Done when each passes locally. - Review threads (GraphQL
reviewThreads): fix them in one commit, or skip the wrong ones. Done when each unresolved thread is fixed or skipped. - CodSpeed: follow
codspeed:codspeed-optimize. Done when green, or the regression is acknowledged with its reason in the PR. - Ecosystem check: read the
Run djangofmt ecosystem checkstep of the job log; the PR comment and job summary are truncated. Every removed line must map to an added line through the PR's intended transformation: strip that change from both sides with a script and multiset-compare. Done when the residue is empty or only line wraps from longer output.
Finish
Push, resolve every step 3 thread with resolveReviewThread without replying, and watch the new run. Report per check what was found, what was done, and the numbers, including skipped threads and anything still red.
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.

