pr-sheriff

Triage pull requests into EASY-WIN, NEEDS-CREW, or NEEDS-HUMAN categories.

17.5k|1.6k|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/gastownhall/gastown --skill pr-sheriff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-sheriff
Source: https://github.com/gastownhall/gastown/tree/main/.claude/skills/pr-sheriff
Command: npx skills add https://github.com/gastownhall/gastown --skill pr-sheriff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR triage is time-consuming and error-prone when dealing with increasing PR volume across repos. This workflow automatically classifies open pull requests into EASY-WIN, NEEDS-CREW, or NEEDS-HUMAN and presents inline recommendations without posting to GitHub.

Core Features & Use Cases

  • Config-driven scope: restricts PR discovery to defined repos (e.g., steveyegge/gastown) to avoid cross-project noise.
  • Inline recommendations: prints suggested actions directly in context rather than posting comments.
  • End-to-end patrol: coordinates loading config, discovering PRs, batch triage, and summary reporting for auditing.

Quick Start

Run the PR Sheriff patrol within the configured scope to triage open PRs.

Frequently Asked Questions about pr-sheriff

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

FAQPage Schema
How do I automate GitHub PR triage for open-source and private repositories?

Automating GitHub PR triage involves running a deterministic, multi-step patrol that categorizes open pull requests into EASY-WIN, NEEDS-CREW, or NEEDS-HUMAN buckets. This process applies a config-driven scope to restrict discovery to defined repos and outputs an auditing summary.

What's the best way to categorize pull requests by review requirements without posting comments to GitHub?

Categorizing pull requests without posting comments requires an inline recommendation system that prints suggested actions directly in context. This approach classifies PRs into easy-wins, crew needs, or human review requirements without writing automated comments back to the GitHub repository.

Can I restrict PR discovery to specific repos to avoid cross-project noise during triage?

Yes, restricting PR discovery to specific repos is supported through a config-driven scope. By defining target repositories in the configuration, the triage patrol limits discovery and categorization strictly to that scope, preventing cross-project noise from affecting the review workflow.

How does batch triage work when processing multiple open pull requests?

Batch triage works by coordinating an end-to-end patrol that loads configuration, discovers open PRs within a defined scope, and triages them in batches. It then outputs a summary report for auditing, ensuring a deterministic classification of each pull request.

Does automated PR triage handle both easy-win identification and complex crew task assignments?

Yes, automated PR triage handles both easy-win identification and complex crew task assignments by classifying pull requests into EASY-WIN, NEEDS-CREW, or NEEDS-HUMAN categories. This classification presents inline recommendations to guide reviewers on which PRs require immediate action versus crew coordination.