babysit

Monitor GitHub pull requests until checks pass and review threads resolve.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill babysit-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: babysit
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/claude-mem/plugin/skills/babysit
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill babysit-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents stalled pull requests by continuously monitoring PR checks, review threads, and new comments until the PR is actually ready to merge.

Core Features & Use Cases

  • PR status monitoring: Watches CI/checks and stops only when checks are passing or intentionally skipped.
  • Review-thread resolution guidance: Detects unresolved review threads and verifies fixes before resolving stale discussions.
  • Evidence-based reporting: Surfaces concrete details like latest commit SHA, unresolved thread count, check names/results, and tests run.

Quick Start

Ask the AI to babysit your pull request #123 so it stays watched until all checks and unresolved review threads are cleared and the PR is ready to merge.

Frequently Asked Questions about babysit

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

FAQPage Schema
How do I monitor a GitHub pull request until CI checks pass and review threads are resolved?

Continuous PR monitoring tracks asynchronous CI runs and new review comments until the pull request is merge-ready. It uses GitHub CLI and GraphQL to detect unresolved threads, verifies applied fixes, and reports the latest commit SHA and check results.

How do I automatically resolve unresolved review threads on a pull request?

Automatically resolving unresolved review threads involves detecting pending discussions via GraphQL and confirming that requested code fixes are applied. The Skill prevents premature thread closure by only resolving discussions after verifying the applied fixes.

What is the best way to keep pull requests moving when CI runs asynchronously?

Keeping pull requests moving during asynchronous CI runs requires continuously polling PR status and handling pending checks. This Skill watches for check completions and new comments, keeping the PR active until it is fully merge-ready.

Does this PR monitoring approach work with GitHub CLI and GraphQL for tracking merge readiness?

Tracking merge readiness works directly with GitHub CLI and GraphQL. The Skill uses these tools to poll PR status, enumerate unresolved review threads, and surface concrete details like latest commit SHA, unresolved thread count, and specific check names.

When should I not use automated pull request babysitting for code review cycles?

Automated pull request babysitting should not be used when asynchronous CI checks are not running or when review threads require manual human judgment outside of verified code fixes. The Skill relies on polling active checks and verifying applied fixes before resolving discussions.