babysit-pr

Monitor GitHub PRs from creation to merge with CI polling and merge readiness detection.

Updated Feb 8, 2026

Search Tags:#automation #github #notifications #ci #pull-request #monitor #daemon

Ready to run

npx skills add https://github.com/ckallum/calsuite --skill babysit-pr-ckallum

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: babysit-pr
Source: https://github.com/ckallum/calsuite/tree/main/skills/babysit-pr
Command: npx skills add https://github.com/ckallum/calsuite --skill babysit-pr-ckallum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs require constant monitoring of CI status, merge readiness, and potential conflicts. This skill automates watching a GitHub PR from creation to merge and notifies you only when attention is required.

Core Features & Use Cases

CI polling with ETag-based checks to reduce redundant requests and stay responsive.
Retry flaky builds once to surface stable results without manual intervention.
Merge readiness detection and real-time conflict alerts to prevent wasted reviews.
Background daemon workflow with local config and non-destructive status tracking for multiple PRs.

Quick Start

Start babysitting a PR by running the babysit-pr command with a PR number to initiate automatic monitoring.

Frequently Asked Questions about babysit-pr

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

FAQPage Schema

How do I monitor GitHub PR CI status automatically until merge?▼

To monitor GitHub PR CI status automatically, you can use a background daemon that polls pull requests from creation to merge using ETag-based checks, notifying you only when attention is needed.

Can I automatically retry flaky CI builds on GitHub pull requests?▼

Yes, you can automatically retry flaky CI builds once to surface stable results without manual intervention, preventing temporary failures from blocking your merge readiness detection.

What is the best way to track merge readiness and conflicts for multiple PRs?▼

The best way to track merge readiness for multiple PRs is a non-intrusive background daemon that maintains local config and non-destructive status tracking files to provide real-time conflict alerts.

How do I reduce redundant API requests when polling GitHub CI?▼

You can reduce redundant API requests when polling GitHub CI by using ETag-based checks, which minimize redundant network calls while staying responsive to pull request status changes.

Do I need external dependencies to run a daemon for PR monitoring?▼

No external dependencies are required to run this PR monitoring daemon, as it operates deterministically using local configuration, status tracking, and log files in a non-intrusive background workflow.