How do I install the Babysit skill?

Run npx skillmds@latest add kevin-liu-01/babysit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Babysit skill do?

Keep a PR merge-ready by triaging comments, resolving clear conflicts, and fixing CI in a loop. It is listed under Coding & Dev Tools on SkillMD.

Is Babysit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Babysit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Babysit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Babysit?

kevin-liu-01 (@kevin-liu-01) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Babysit by kevin-liu-01 — Agent Skill

Name: Babysit
Author: kevin-liu-01

File contents

Babysit PR

Your job is to get this PR to a merge-ready state.

Check PR status, comments, and latest CI and resolve any issues until the PR is ready to merge.

Merge conflicts: Intelligently resolve any merge conflicts, preserving the intent and correctness of changes on your branch and the base branch. If intents conflict, abort the merge and ask for clarification.
Comments: Review active unresolved comments (including Bugbot) and resolve change requests / bug reports where valid. When fetching GitHub comments, filter out resolved threads first. Read only each comment body and the minimum location/URL needed to act on it; do not read the entire JSON output or other unnecessary payload data. Carefully validate issues reported by Bugbot and only take action on those that are valid; explain when you disagree or are unsure.
CI: Fix CI issues caused by changes within this PR's scope. Never change CI checks/workflows just to make failures pass, or make unrelated code changes; if that would be required, report back instead. For merge-blocking failures that seem unrelated to this PR, check whether the branch is behind the base branch and merge latest changes, since another PR may have fixed them. Push scoped fixes and re-watch CI until mergeable + green + comments triaged.

Frequently asked questions

Babysit