pr-shepherd

Monitor a GitHub Pull Request through merge, handling CI failures and review comments.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/jpeggdev/buildwithjpegg --skill pr-shepherd-jpeggdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-shepherd
Source: https://github.com/jpeggdev/buildwithjpegg/tree/main/plugins/tribunal/skills/pr-shepherd
Command: npx skills add https://github.com/jpeggdev/buildwithjpegg --skill pr-shepherd-jpeggdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the tedious process of monitoring a Pull Request (PR) through to its successful merge, handling CI failures, review comments, and thread resolutions without constant human intervention.

Core Features & Use Cases

  • Automated Monitoring: Continuously checks CI status and review comments.
  • Auto-Fixing: Attempts to resolve common CI failures (lint, type, test) using TDD.
  • Review Handling: Integrates with handling-pr-comments skill to address feedback.
  • Use Case: After creating a PR, activate this skill to ensure it passes all checks, addresses feedback, and merges without you needing to babysit the process.

Quick Start

Use the pr-shepherd skill to monitor the current PR until it is merged.

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 pull request until it merges?

To automatically monitor a GitHub pull request until it merges, you can use an automated monitoring skill that continuously checks CI status, addresses review comments, and attempts to merge the PR without manual intervention.

Can I auto-fix CI failures like lint and type errors on a pull request?

Yes, you can auto-fix common CI failures like lint, type, and test errors on a pull request by utilizing an automated fixing mechanism that applies TDD-based resolutions during the PR monitoring lifecycle.

What is the best way to handle review comments and thread resolutions automatically in GitHub?

The best way to handle review comments and thread resolutions automatically in GitHub is to use a monitoring tool that integrates with comment resolution skills, actively transitioning between monitoring and review handling states to address feedback.

Do I need the gh CLI to automate pull request merging and status checks?

Yes, you need the `gh` CLI to automate pull request merging and status checks, as the monitoring process relies on it alongside `gtg` to query CI statuses and manage the PR lifecycle.

How does a PR monitoring tool handle the lifecycle from CI checks to final merge?

A PR monitoring tool handles the lifecycle from CI checks to final merge by operating through defined states like MONITORING, FIXING, and HANDLING_REVIEWS, automatically resolving failures and feedback until the PR merges.

Why does my automated PR workflow get stuck handling review threads?

Automated PR workflows may get stuck handling review threads if the monitoring tool lacks proper integration with comment resolution skills, preventing it from transitioning out of the HANDLING_REVIEWS state to complete the merge.