shepherd
Shepherd Skill
VCS Provider
This skill uses VCS operations through Exarchos MCP actions (check_ci, list_prs, merge_pr, get_pr_comments, add_pr_comment, etc.).
These actions automatically detect and route to the correct VCS provider (GitHub, GitLab, Azure DevOps).
No gh/glab/az commands needed — the MCP server handles provider dispatch.
The
merge_prinvoked here is the remote PR merge primitive (synthesize-phase). It is distinct from the integration merge run during the upstreammerge-pendingsubstate — there,serialize_merge(@skills/merge-orchestrator/SKILL.md) is the integration-merge path: it holds a single-writer lease and composes the localgit merge(rawmerge_orchestrateis that composed executor / the non-integration path). This skill never invokesserialize_mergeormerge_orchestrate.
Iterative loop that shepherds published PRs through CI checks and code reviews to merge readiness. Uses the assess_stack composite action for all PR health checks, fixing failures and addressing feedback until the stack is green.
Note: Shepherd is not a separate HSM phase. It operates as a loop within the
synthesizephase. The workflow phase remainssynthesizethroughout the shepherd iteration cycle. Events (shepherd.iteration,ci.status) and theshepherd_statusview track loop progress without requiring a phase transition.
Position in workflow:
synthesize → shepherd (assess → fix → resubmit → loop) → cleanup
^^^^^^^^^ runs within synthesize phase