babysit

Manage comments, resolve merge conflicts, and fix CI issues for a pull request.

Updated Mar 4, 2026

Search Tags:#code review #pull request #github #continuous integration #triage

Ready to run

npx skills add https://github.com/shankur/dots --skill babysit-shankur

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: babysit
Source: https://github.com/shankur/dots/tree/main/dot_cursor/skills-cursor/babysit
Command: npx skills add https://github.com/shankur/dots --skill babysit-shankur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill automates the process of maintaining PRs ready for merging by handling comments and continuous integration issues.

Core Features & Use Cases

PR Triage: Manage comments, conflicts, and CI issues for a pull request.
Merge Conflicts Resolution: Identify and resolve merge conflicts preserving change integrity.
Comment Handling: Address and resolve comments and bug reports promptly.
CI Management: Fix CI issues within the scope of the PR and watch for successful merges.
Use Case: When working on a pull request that requires attention to both code changes and CI pipeline.

Quick Start

To babysit a pull request and keep it ready for merging, execute the 'babysit' skill command.

Frequently Asked Questions about babysit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate pull request triage for faster merging on GitHub?▼

Automating pull request triage involves monitoring PR comments, resolving merge conflicts, and handling continuous integration pipelines. This skill manages those elements automatically to maintain PR merge readiness by interacting directly with the GitHub API.

What is the best way to keep a pull request ready for merging while CI runs?▼

Keeping a pull request ready for merging requires managing CI pipelines and addressing code review comments. This skill handles CI issues and monitors comments within the PR scope, watching for successful pipeline completion to ensure merge readiness.

Can I automatically resolve merge conflicts in a GitHub pull request?▼

Resolving merge conflicts automatically is possible by identifying conflict markers and fixing them while preserving change integrity. This skill automates conflict resolution as part of its PR triage process to keep your pull request ready for merging.

Do I need GitHub API access to manage comments and CI on a pull request?▼

GitHub API access is required to interact with pull request data, manage comments, and monitor continuous integration. This skill uses the API to automate the triage process, handle bug reports, and fix CI issues for the given PR.

How do I handle code review comments and bug reports on a pull request automatically?▼

Handling code review comments and bug reports automatically requires monitoring PR activity and addressing feedback promptly. This skill addresses and resolves comments within the scope of the PR to maintain continuous merge readiness.

Why does continuous integration fail on my pull request and how can I fix it?▼

Continuous integration fails on pull requests due to test failures, build errors, or configuration issues. This skill handles CI management by fixing CI issues within the scope of the PR and watching for successful merges to ensure merge readiness.