skills.rest
arthur-debert
arthur-debertCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

shepherding-prs

Manage pull request review threads in severity order across rounds.

Updated Apr 14, 2026
Search Tags:#code review#pull request#github#verification#severity triage#review threads
One-click install
npx skills add https://github.com/arthur-debert/dodot --skill shepherding-prs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shepherding-prs
Source: https://github.com/arthur-debert/dodot/tree/main/.agents/skills/shepherding-prs
Command: npx skills add https://github.com/arthur-debert/dodot --skill shepherding-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you shepherd one open pull request through successive review rounds without losing track of reviewer feedback, required fixes, or verification steps.

Core Features & Use Cases

  • Review triage: Re-read the PR, current diff, and open threads at the start of every round so you work from the latest source of truth.
  • Severity-ordered fixes: Address findings in the required critical, major, minor, then nit order, either by fixing the code or replying with a rationale.
  • Thread resolution and verification: Resolve every open thread, run the exact verify commands from the brief, and push the round together before parking.
  • Use case: A developer hands off an in-progress PR after review comments land, and you methodically clear them while keeping the work aligned with the governing spec and decision boundaries.

Quick Start

Read the current PR state, fix or respond to each open review thread in severity order, verify with the prescribed commands, and then push the round and hand it back to the coordinator.

Frequently Asked Questions about shepherding-prs

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

FAQPage Schema
How do I manage GitHub pull request review threads across multiple rounds?▼

To manage GitHub pull request review threads across multiple rounds, reread the latest diff and address open threads in severity order—critical, major, minor, then nit—by either fixing the code or replying with a rationale.

What is the best way to triage code review findings on a pull request?▼

The best way to triage code review findings on a pull request is to process them by severity, handling critical issues first, followed by major, minor, and nit findings, ensuring fixes align with the governing spec.

How do I verify code changes before pushing a pull request review round?▼

To verify code changes before pushing a pull request review round, run the exact verify commands specified in the brief, resolve every open review thread, and coordinate the push-and-park behavior without manually merging.

Can I use severity-ordered fixes for GitHub PR shepherding without manually merging?▼

Yes, severity-ordered fixes for GitHub PR shepherding work without manually merging by rereading the current PR state, addressing findings in critical, major, minor, and nit order, then pushing the round and handing it back to the coordinator.

When do I need to preserve decision boundaries during pull request shepherding?▼

You need to preserve decision boundaries during pull request shepherding whenever addressing reviewer feedback, ensuring that fixes or rationale replies stay aligned with the governing spec and do not expand the scope of the open pull request.

Related Skills

Explore More Software Engineering Skills→
dimagidimagi
3

iterate-pr

Automate fixing CI failures and replying to GitHub pull request review threads.

Official
Advanced
khapn-2933khapn-2933

tkm:ship

Automate GitHub release steps for feature branches with conditional flags.

Community
Advanced
liujiayi3703liujiayi3703

babysit

Monitor pull request status and manage review threads via GitHub CLI.

Community
Intermediate
D3HunterD3Hunter

merge-review-json-and-submit-pr-review

Merge review JSON files and submit consolidated GitHub PR reviews.

Community
Intermediate