shepherd
Shepherd PR
Your job is to shepherd this PR all the way to merge-ready - reviewed, addressed, verified, and CI green. Not merged. Merging is a human decision.
Create the PR (or pick up the one just created), mark as ready for review if not yet the case, then relentlessly poll its status in a loop. Do not stop polling until all automatic reviewers (e.g., Bugbot, Cubic, etc) have fully completed their review.
-
Wait for reviewers: Keep polling
gh pr view/gh pr checks/ review comments until ALL reviewers have finished. Do not act on partial feedback. If one is still running, keep waiting. -
Triage their feedback: Once both are done, implement their required changes. Fix everything medium severity and beyond. Only fix low severity issue if they're a DRY violation or if there are other issues to fix already. Strictly skip suggestions/low severity issue if they're the only ones remaining, and they qualify under super minor (nit) or rare edge case. In these cases reply explaining why and continue working autonomously.
-
Commit and push: After implementing changes, commit and push. Then go back to step 1 - the reviewers will automatically re-review your new push.
-
Loop: Repeat until a full cycle passes with nothing meaningful left to address from either reviewer.
-
Double-verify merge-ready: Before declaring the PR merge-ready, verify twice that (a) all reviewers have re-run on the latest commit, (b) no outstanding required changes remain, and (c) CI is green and the PR is mergeable.
-
Stop. Hand off to human. Report that the PR is merge-ready and wait. Do not merge.
Hard rule: never merge without explicit approval
- NEVER run
gh pr merge, the GitHub merge API, or any equivalent action on your own. - "All checks green" is NOT permission to merge. It is permission to stop and report.
- Even if the user originally said "get this PR merged", treat that as "get this PR merge-ready" and ask for explicit confirmation before merging.
- Only merge if the user replies with an explicit, unambiguous YES to merge after you've reported merge-ready (e.g. "yes merge it", "go ahead and merge"). A thumbs-up or "ok" is not enough - ask again if unclear.
- If in doubt, do not merge. Ask.
"Pushed a fix" is not done. "All green" is not done either - it's the handoff point.
Do not stop early. Do not merge on your own.
Done is when you've looped through a clean review cycle, double-checked it, reported merge-ready, and the human has explicitly approved the merge.
More from robinebers/skills
code-auditor
Audit codebases for duplicate code, unused code, DRY violations, dependency bloat, and refactoring opportunities. Use when the user asks for a code audit, technical debt review, dead-code cleanup, dependency audit, consolidation plan, or maintainability review after major feature work or before refactoring.
8code-upgrade
Engineering-discipline toolkit for non-technical users working with AI coders. Wields KISS, DRY, YAGNI, fail-fast, and idempotency as commands. Use when the user asks to audit, simplify, clean up, dedupe, or harden code; or says "make this simpler", "any duplicates?", "is this safe to run twice", "explain this app", "find dead code", "simplify the plan", or "find silent failures".
7setup-process
Generate setup scripts/configs for AI agent worktrees and isolated environments across Cursor, Codex, and Conductor. Use when wiring up a project so AI agents start with the same dependencies, env files, and tool configs as the main repo.
5agents-md
Install or update Robin Ebers's AGENTS.md from github.com/robinebers/agents.md. Use when the user asks to add AGENTS.md to a workspace, refresh it to the latest upstream version, merge upstream changes into a customized local AGENTS.md, or make the repo follow Robin's agent protocol file.
3pr-manager
Manage GitHub pull requests with `gh` and `git`: create or update a pull request, wait for checks, fetch review comments, and optionally fix them automatically. Use when the user says things like "create pr", "open a pr", "update the pr", "pull comments", "check PR comments", "check for new comments", or "fetch review comments".
3conductor-json
Generate conductor.json files for Conductor workspaces. Use when setting up a new project, creating conductor.json, or configuring workspace scripts for Tauri, Next.js, or React projects.
2