github_pro_babysitter

Audits GitHub repositories for stale PRs, failing workflows, and noisy issues into a health digest.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Scattered GitHub signals across many repositories make it hard to spot blocked pull requests, failing Actions workflows, and stale issues before they become problems. This Skill consolidates those signals into a single prioritized health digest without making any external changes. ## Core Features & Use Cases - Repo Health Scoring: Scores each repository from 0 to 100 across workflow health, PR state, issue staleness, dependency risk, and automation noise. - PR and Issue Classification: Categorizes open PRs as blocked, stale, ready, or conflict-risk, and flags stale, priority, or bot-generated noisy issues. - Workflow Monitoring: Detects failure streaks on default branches and repeatedly failing scheduled or dependency-update runs. - Use Case: Run a daily read-only scan of all repos under an organization to produce a digest of blocked PRs, failing workflows, and recommended next actions, while explicitly listing actions not taken. ## Quick Start Ask the assistant to check health for a repository such as darksheer/ARC and produce a digest of stale PRs and failing workflows.

Frequently Asked Questions about github_pro_babysitter

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

FAQPage Schema
How do I monitor GitHub repo health across an organization?

Run the skill against an organization to list repos, collect open PRs, issues, and workflow runs, then classify and score each repo. It produces a digest with a scorecard, top risks, and recommended actions without making external changes.

How to find stale PRs and failing GitHub Actions workflows?

The skill fetches open PRs and recent workflow runs per repo, then flags PRs stale beyond the configured threshold and workflows with failure streaks on the default branch. Results are grouped into a report with recommended next actions.

Does this skill merge PRs or post comments automatically?

No. Write actions default to false, so it never merges, closes, comments, reruns, or labels anything unless the user explicitly asks. Recommended actions are listed in the report under actions not taken.

What GitHub access is required for repo monitoring?

It prefers the GitHub MCP connector, falls back to an authenticated GitHub CLI session, and finally to REST API calls with a GITHUB_TOKEN environment variable. Only read access is needed for monitoring mode.

Should I use github_pro_babysitter or github-babysitter?

Use github-babysitter with repo-rounds mode for new work. This legacy skill exists only for old prompts, existing .github-pro-babysitter.yml configs, or migration compatibility checks.