run-health-review

Unattended work fails quietly. A host restarts and children sit idle, a quota runs out at 2am, a prompt drifts, the pool empties, CI goes red and every worker politely no-ops. Without a watchdog, the human computes "time since last merge" by eye every morning. This skill makes that check a job: measure health from GitHub state, name the stall, change one thing (or nothing), and pick up work that was left half-done.

When to use

• "Why did delivery stall overnight?", "nothing merged for 8 hours", "this was great the first few days, now it's slow".
• An automation failed (automation_failed) or its useful-output rate dropped.
• 403/429 rate-limit errors, or CI minutes or another quota ran out.
• On a schedule: every 30–60 minutes during an active unattended run; weekly for automations at steady state.

When not to use

• Nothing is running unattended. Use progress-contract for attended work.
• A single PR is red. That is pr-shepherd's job.

Steps