babysit

Triage GitHub comments, resolve merge conflicts, and repair PR-scoped CI failures.

Updated May 18, 2025
One-click install
npx skills add https://github.com/nthpaul/dotfiles --skill babysit-nthpaul
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: babysit
Source: https://github.com/nthpaul/dotfiles/tree/main/cursor/.cursor/skills-cursor/babysit
Command: npx skills add https://github.com/nthpaul/dotfiles --skill babysit-nthpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A PR can linger in review because of unresolved conflicts, outdated or missing context, and failing CI checks, keeping the team blocked from merging.

Core Features & Use Cases

  • Merge conflict resolution: Resolve merge conflicts while preserving intended changes, and stop to request clarification when intents fundamentally conflict.
  • Comment and bug triage: Review active unresolved GitHub comments (including Bugbot) and resolve only valid change requests by acting on minimal required details.
  • CI repair loop: Fix merge-blocking CI failures caused by the PR’s scope, avoid unrelated workflow changes, and re-check until the PR is mergeable with CI green and comments triaged.

Quick Start

Tell the AI to babysit this pull request and get it to a merge-ready state by resolving conflicts, triaging unresolved comments, and fixing only PR-scope CI failures until everything is mergeable and green.

Frequently Asked Questions about babysit

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

FAQPage Schema
How do I fix failing CI checks and resolve merge conflicts on a blocked pull request?▼

To fix failing CI checks and resolve merge conflicts on a blocked pull request, triage unresolved review comments and repair PR-scoped CI failures iteratively until the branch is merge-ready and green.

What is the best way to triage unresolved GitHub comments on a pull request?▼

Triage unresolved GitHub comments by parsing active threads, excluding already resolved feedback, and addressing only valid change requests based on minimal required details to reach a merge-ready state.

How do I handle merge conflicts when the base branch intent is unclear?▼

When handling merge conflicts against base branch intent, interpret changes safely to preserve intended updates, but stop and request clarification if the intents fundamentally conflict to avoid unintended overwrites.

Can I use this to fix continuous integration failures without modifying unrelated workflows?▼

Yes, you can fix continuous integration failures with constrained remediation that targets only PR-scoped changes, deliberately avoiding modifications to unrelated workflows to keep the pipeline stable.

Why does a pull request stay blocked in review even after passing CI checks?▼

A pull request stays blocked in review even after passing CI checks if unresolved GitHub comments remain open or merge conflicts exist, requiring active comment triage and conflict resolution before merging.