pr-shepherd
PR shepherd
Most of the work between "PR opened" and "change shipped" is babysitting: watching CI, rerunning a flaky job, answering review threads, rebasing, and merging once everything is green. This skill turns that work into an event-driven loop with three exit gates. Green on the exact head. Every thread dispositioned. Landed at the level the dial allows. Each wake reads state once, takes the next useful action, writes a record and stops. The next event (a push, a finished check, a review, a conflict) wakes it again. It never sleeps inside a turn or polls in a loop, and it never weakens a check to get to green.
You can run it locally (a session with a self-wake or session automation) or in the cloud as a GitHub Copilot Automation. The cloud recipe is in automations/pr-shepherd/. Both use the same contract, so a manual run and an automated run behave identically.
When to use
- You are about to type "monitor CI and push fixes until green", or you already have.
- A PR has red required checks, unresolved threads or a merge conflict, and you want it handled without watching it.
- A coordinator (
autonomous-delivery) has green-but-unlanded PRs to hand off.
Don't use it for:
- Ordering and batching many PRs into a merge queue. Use
landing-plan, which calls this skill per PR. - Red CI on the default branch with no PR involved. That's main-red triage (see the automation recipes).
- PRs whose author or owning team hasn't opted in. On repos you don't own, stay at L0 or L1 and comment only.