shepherd

Assess pull requests against CI checks and reviews until merge readiness.

33|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/lvlup-sw/exarchos --skill shepherd-lvlup-sw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shepherd
Source: https://github.com/lvlup-sw/exarchos/tree/main/skills-src/shepherd
Command: npx skills add https://github.com/lvlup-sw/exarchos --skill shepherd-lvlup-sw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Shepherd PRs through CI checks and code reviews to merge readiness, operating as a loop inside the synthesize phase rather than a separate HSM phase.

Core Features & Use Cases

  • Assess PR health across CI checks and inline reviews to drive timely fixes
  • Iterate through fix, resubmit, and approval-request cycles until all gates pass
  • Emit lifecycle events for telemetry and governance to support observability

Quick Start

Trigger the shepherd loop for a feature and let it iterate through assessment, fixes, and resubmission until all checks pass.

Frequently Asked Questions about shepherd

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

FAQPage Schema
How do I automate PR merge readiness through CI checks and code reviews?

Automating PR merge readiness involves running an iteration loop that pairs pull requests with CI checks and inline reviews, performing assessment, fixes, resubmission, and approval requests until all gates pass green.

What is the best way to iterate through PR fixes and resubmission cycles automatically?

The best way to iterate through PR fixes is triggering a synthesize phase loop that assesses PR health, applies necessary fixes, resubmits the code, and requests approvals until all CI and review gates pass.

Does this PR automation workflow integrate with telemetry and governance systems?

Yes, the PR automation workflow integrates with governance and telemetry systems by emitting lifecycle events during the iteration loop, providing observability and compliance tracking across the merge readiness process.

Can I use this code review automation without adding a separate state machine phase?

Yes, you can automate code review without a separate state machine phase because the iteration loop operates directly inside the synthesize phase, continuously assessing and fixing PRs until merge readiness is achieved.

What are the limitations of automating merge readiness deterministically?

Limitations of deterministic merge readiness automation include dependency on the assess_stack composite integration and the requirement to continuously iterate through fixes and approval requests until all CI checks successfully pass.

Why does my PR assessment loop fail to reach merge readiness?

Your PR assessment loop may fail to reach merge readiness if CI checks continuously fail, inline review comments are not resolved, or the fix, resubmit, and approval-request cycle cannot iterate until all gates pass green.