pr-shepherd

Monitors GitHub pull requests through CI failures and review comments until merge.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/seal-harness/seal-harness --skill pr-shepherd-seal-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-shepherd
Source: https://github.com/seal-harness/seal-harness/tree/main/.agents/skills/pr-shepherd
Command: npx skills add https://github.com/seal-harness/seal-harness --skill pr-shepherd-seal-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After a pull request is created, someone must watch CI checks, fix failures, respond to review comments, and resolve threads before merge. This Skill automates that entire monitoring loop so the agent owns its PR lifecycle without constant human supervision. ## Core Features & Use Cases - Continuous PR Monitoring: Polls CI status and review threads every 60 seconds using GTG (Good-To-Go) as a single readiness check, with manual gh CLI fallbacks. - Autonomous Fixing: Auto-fixes lint, formatting, type errors, and test failures using TDD, with local validation (lint, typecheck, tests, coverage) required before every push. - Review Comment Handling: Delegates to the handling-pr-comments skill with an enforced iteration loop so no new comments are missed after pushes. - Escalation & Handoff: Presents structured options for complex issues, checkpoints every 4 hours, and supports clean handoff or post-merge knowledge extraction. - Use Case: An agent working in a git worktree creates a PR, then shepherds it in the background — fixing a failing lint check, replying to a CodeRabbit comment, resolving all threads, and reporting when the PR is merged. ## Quick Start Ask the agent to shepherd the pull request you just created by saying "monitor PR #123 through to merge and handle any CI failures or review comments".

Frequently Asked Questions about pr-shepherd

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

FAQPage Schema
How do I automatically monitor a GitHub PR until it merges?

Invoke the pr-shepherd skill with the PR number after creating the PR. It polls CI status and review threads every 60 seconds using GTG, fixes failures, responds to comments, and exits only when all checks pass and all threads are resolved.

How does the skill handle CI failures on a pull request?

Simple failures like lint, formatting, type errors, and test failures in agent-written code are auto-fixed using TDD, then validated locally with lint, typecheck, tests, and coverage before pushing. Complex or ambiguous failures are escalated to the user with structured options.

Can pr-shepherd respond to code review comments automatically?

Yes, it delegates to the handling-pr-comments skill, which categorizes comments, applies fixes, replies, and resolves threads. An enforced iteration loop re-checks for new comments after each push so nothing is missed.

What happens if the PR review process takes many hours?

At the 4-hour mark the skill pauses and presents a checkpoint with options: keep monitoring, exit with a status handoff, or switch to shorter check-ins. A handoff report lets you resume later with the same command.

When should I not let the agent auto-fix PR issues?

Auto-fix is limited to lint, formatting, type errors, and tests in code the agent wrote. Test failures in unfamiliar code, infrastructure or config failures, and ambiguous errors always require user approval before any fix is attempted.