agentleFS
Sign inStart free
leighstillardleighstillard/coach-ship-skills/skills/babysit/SKILL.md

babysit

Skill2 starsChanged 5 months agoMITView on GitHub

Shepherd an open PR to merge. Watches CI, fixes failures, addresses review comments, resolves conflicts, and enables/executes merge when green. Use after opening a PR, when the user says babysit/watch/get this merged, or as the final step of /ship.

45 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • tuliosalustiano27Skill

    oh-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

  • tuliosalustiano27Skill

    what-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

  • Tsumugii24Skill

    split-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

  • mukcoSkill

    principles

    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

  • PandelisZSkill

    update-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

  • 32103210Skill

    migrate-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

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Wait 60-120 seconds between unchanged pending states.

    line 17
  2. Very specific:

    Read the actual failure log: gh run view <run-id> --log-failed.

    line 20
  3. Distinctive:

    Do not mark reviewer threads resolved unless repo convention says authors resolve.

    line 31
  4. Very specific:

    Use --force-with-lease after a rebase, never bare --force.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 43 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Babysit

Goal

The PR merges, or you stop with a precise blocker and the evidence for it.

Loop

Poll without spinning:

gh pr view <number> --json state,reviewDecision,mergeable,comments,headRefName,baseRefName
 gh pr checks <number>

Wait 60-120 seconds between unchanged pending states.

CI failed

  1. Read the actual failure log: gh run view <run-id> --log-failed.
  2. Classify:
    • caused by this diff → fix, run local verification, commit, push.
    • flaky/infra → retry once; if it repeats, treat as real or escalate.
    • broken on base branch → prove or cite evidence, then stop; do not absorb main's failure into this PR.
  3. Loop guard: after 3 distinct failed fix attempts for the same check, stop and summarize attempts.

Review comments arrived

  • Address substantive comments in code, batching fixes where practical.
  • Reply with what changed or a concise rebuttal.
  • Escalate genuine disputes after at most two back-and-forths.
  • Do not mark reviewer threads resolved unless repo convention says authors resolve.

Merge conflict

  • Fetch and rebase/merge according to repo convention.
  • Resolve conservatively; inspect both sides' intent before choosing.
  • Re-run relevant tests and verification before pushing.
  • Use --force-with-lease after a rebase, never bare --force.

All green + approved

  • Determine merge convention from repo settings/recent PRs.
  • Enable auto-merge or merge directly as appropriate, e.g. gh pr merge <number> --auto --squash.
  • Confirm the PR state is merged and report the URL/merge commit if available.

Exit conditions

Stop when:

  • merged
  • blocked on human review with no actionable comments
  • loop guard tripped
  • failure requires a product/security/API/data decision
  • credentials/permissions are missing

Gotchas

  • gh pr checks can return non-zero while pending; read the output.
  • Pushing fixes can dismiss approvals; batch review fixes.
  • External checks you cannot inspect/retry are blockers, not reasons to wait forever.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free