babysit-pr

Opens a pull request and polls CI until all checks pass, fixing failures along the way.

21|1|Updated Jul 22, 2026
One-click install
npx skills add https://github.com/uiverify/uiverify --skill babysit-pr-uiverify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: babysit-pr
Source: https://github.com/uiverify/uiverify/tree/main/packages/skills/skills/babysit-pr
Command: npx skills add https://github.com/uiverify/uiverify --skill babysit-pr-uiverify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening a pull request is only half the work — CI failures, flaky checks, and visual regressions demand repeated rounds of log reading, fixing, and re-pushing. This Skill automates that babysitting loop so a branch reaches a green, merge-ready state without manual polling. ## Core Features & Use Cases - PR creation from the real diff: Generates the title and body from git diff against the base branch, runs the local gate (format, lint, typecheck, test) before pushing, and is idempotent if a PR already exists. - CI babysit loop: Watches checks with gh pr checks --watch on a ~10-minute cadence, reacts to each failure by reading the failing job's logs, fixing locally, and pushing until everything is green. - Failure triage and lesson capture: Distinguishes lint/test failures, flaky infra failures (re-run once), and visual regressions (triaged via the triage-visual-changes skill), and proposes capturing generalizable mistakes as rules via /add-rule. - Use Case: After finishing a feature branch, ask the agent to raise a PR and watch it; it fixes a typecheck failure, triages a UI Verify visual diff, and hands back a green PR ready for a human to merge. ## Quick Start Ask the agent to raise a PR from the current branch and babysit it until every CI check is green.

Frequently Asked Questions about babysit-pr

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

FAQPage Schema
How do I automatically fix CI failures on a GitHub pull request?▼

This Skill polls PR checks with the GitHub CLI, reads the failing job's logs via gh run view --log-failed, reproduces the failure locally, fixes it, and pushes. The fresh CI run then confirms the fix, repeating until all checks pass.

How to monitor GitHub PR checks without constant polling?▼

It runs gh pr checks --watch in the background as a notifier paired with a single scheduled wakeup (~600s) as a fallback heartbeat. This avoids burning tool calls on tight polling loops while still reacting when checks settle.

Can this skill merge or approve my pull request?▼

No. The skill deliberately never approves or merges; green and ready-to-merge is its terminal state. A human performs the final merge as an intentional review gate.

How are visual regression failures handled in CI?▼

Visual regression signals are triaged through the triage-visual-changes skill, comparing baseline and candidate images per story. Intended changes get their baselines accepted; regressions are fixed in code, and blanket-accepting baselines is forbidden.

What happens if the same CI check keeps failing?▼

If the same check fails across roughly three fix attempts with no progress, the skill stops and surfaces the issue for a human decision instead of churning CI indefinitely. Flaky infra failures are re-run once before being treated as real.