Babysit

CommunityPopular

michael-denyer

babysit

Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.

Overview

Publisher	michael-denyer
Repository	`pstack-claude`
Skill name	`babysit`
Stars	1.2K
Forks	139
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by michael-denyer on GitHub. Read the source before you install it.

Installation

Install the Babysit AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/michael-denyer/pstack-claude/tree/main/plugins/pstack/skills/babysit
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/michael-denyer/pstack-claude.git /tmp/pstack-claude
mkdir -p .claude/skills
cp -r /tmp/pstack-claude/plugins/pstack/skills/babysit .claude/skills/babysit

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Babysit in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Babysit on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Babysit is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Babysit a PR

On Codex, read the platform mapping, including its per-skill notes, before following this skill.

Claude Code analog of Cursor's built-in /babysit. The implementation is a loop over gh CLI plus the Claude Code loop skill for pacing.

Inside poteto-mode, the Babysit playbook (../poteto-mode/playbooks/babysit.md) supersedes this skill: it owns mode declaration, the merge frontier, stack safety, and the watch-pr watcher. This skill stays the standalone /babysit entry point for a single PR outside a poteto-mode run.

When to use

There's an open PR and the user explicitly wants it kept green, and you are not already inside a poteto-mode run (the playbook owns that case).
The user invokes /babysit directly.
A subagent that opens a PR does NOT babysit — return to the parent and let the parent decide.

Steps

Fetch PR state.

bash
gh pr view <number> --json number,title,state,mergeable,reviewDecision,statusCheckRollup,mergeStateStatus,comments,reviews

Triage in priority order.
- Merge conflicts (mergeStateStatus == DIRTY): run the fix-merge-conflicts skill. Force-push only if the branch is yours and not shared.
- Failing checks (statusCheckRollup entries with conclusion: FAILURE): run the fix-ci skill. Root-cause the failure; fix the underlying code or test; commit; push.
- Review comments: run the get-pr-comments skill for the summary, then act only on feedback you actually agree with. When a comment has a single mechanical answer — a rename, a guard clause, a formatting nit — make the edit and quote the comment in the commit message. When it hinges on a judgement call, or you can't tell what's being asked, don't guess: leave it and reply with what you would have done.
- Review-bot comments (Bugbot and similar automation): classify fix/dismiss/ask before acting, per bugbot-triage.md. Ask by default on security, data, and high-severity findings.
Loop. Use the Claude Code loop skill to pace re-checks. Pick the interval from what you're watching:
- Active CI run: poll gh pr checks --watch (it blocks until checks finish, so no separate loop interval needed).
- Awaiting reviewer: 20–30 min heartbeat.
- Idle but want to catch new comments: hourly.
When to stop.
- Build is green, every comment resolved, branch merges cleanly → call it ready.
- You've run three rounds of fix → push → recheck and it still isn't fully green → stop, summarise what's still broken, and hand control back.
- The next fix would force a design choice → pause and put it to the user with AskUserQuestion.
Report. Summarize fixes applied, comments addressed, comments deferred (with reason), current PR status. Cite each commit by SHA.

Hard rules

Don't rewrite history on a branch others may have pulled. If a rebase or force-push looks necessary, clear it with the user first.
Don't tweak a test's expected values just to get a pass. Only change an assertion when the behaviour genuinely changed and the assertion was pinned to the old behaviour.
Never skip hooks (--no-verify).
Never bypass a failing check by marking it as not required.
gh pr ready only when all checks are green and no unresolved review comments remain.

Cross-refs

Opening a PR does not start a babysit; inside poteto-mode the Babysit playbook owns the request and starts only when asked.
Use interrogate before opening if the diff is contested; once open, babysit takes over.
Use unslop on any prose you write here (PR comments, commit messages, status reports).

Provenance

This is a Claude Code analog of Cursor's /babysit, not a port — Cursor's implementation is closed source. The skill is independently authored, with its own prose and structure; the workflow is informed by Cursor's public /babysit behavior. The only overlap with other PR tools is the gh CLI commands it runs, which are functional invocations rather than copied text.

Frequently asked questions

What does the Babysit AI skill do?

Why use Babysit on TypingMind?

Because you install it once and use it with any model. Babysit is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Babysit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/michael-denyer/pstack-claude/tree/main/plugins/pstack/skills/babysit. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Babysit?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Babysit?

As many as you like. As long as a model supports skills, you can use Babysit with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Babysit AI skill free?

Yes. It is published on GitHub by michael-denyer under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Gitcrawl

openclaw

OrganizationPopular

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Graincrawl

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Babysit a PR

When to use

Steps

Hard rules

Cross-refs

Provenance

Frequently asked questions

Related AI Skills

Set up your own AI workspace now