github-babysitter

Triage GitHub PRs, CI failures, and repo health through iterative state-transition loops.

Updated May 10, 2026
One-click install
npx skills add https://github.com/darksheer/agentic-skills --skill github-babysitter-darksheer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-babysitter
Source: https://github.com/darksheer/agentic-skills/tree/main/plugins/agentic-skills/skills/github-babysitter
Command: npx skills add https://github.com/darksheer/agentic-skills --skill github-babysitter-darksheer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Open pull requests stall on failing CI, unresolved review comments, and unclear merge readiness, forcing developers to manually inspect checks, reviews, and workflows across repositories. ## Core Features & Use Cases - PR-Care Loop: Iteratively inspects a PR's checks, reviews, and comments, applies or plans fixes, and drives it toward ready-to-merge, merged, or a concrete blocked state. - Repo-Rounds Health Scans: Scores repositories 0-100 based on workflow health, open PRs, stale issues, dependency signals, and automation noise. - Review Tool Triage: Normalizes and deduplicates findings from CodeRabbit, Codex, Jules, Gemini, Reviewdog, and other bots, with an approval queue gating every external write. - Use Case: After a Jules session promotes a PR, hand the payload to this Skill to triage failing checks, address review comments, and report exact merge readiness with an approval queue. ## Quick Start Ask the agent to run github-babysitter on the current repository's open pull requests and report which ones are ready to merge.

Frequently Asked Questions about github-babysitter

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

FAQPage Schema
How do I check if a GitHub pull request is ready to merge?

Run the pr-care mode on the PR URL or number. It inspects checks, review decisions, unresolved threads, and mergeability, then reports a verdict of ready-to-merge, blocked, or unknown with concrete evidence for each blocker.

How do I triage failing GitHub Actions checks on a PR?

The CI triage flow identifies the failing workflow, job, and step, reads summaries before full logs, attributes the root cause, and recommends one action such as fixing code, updating a test, or rerunning a flaky job.

Can it handle CodeRabbit, Codex, and Gemini review comments?

Yes. It normalizes findings from CodeRabbit, Codex, Jules, Gemini, PR-Agent, Graphite, and Reviewdog into a common schema, deduplicates them by file and range, and evaluates each for accuracy before applying or deferring fixes.

Does it post comments or merge PRs automatically?

No. All external writes including comments, labels, reruns, pushes, and merges require exact approval first. Read-only inspection, classification, and local fix planning run without approval, and write_actions defaults to false in config.

What configuration file does github-babysitter use?

It reads .github-babysitter.yml for modes, scoring weights, review tool trust levels, and reporting options. Legacy .pr-orchestrator.yml and .github-pro-babysitter.yml files are understood for migration but new setups should use the new file.