repo-pr-triage
por patrob
Git & GitHubResumo
Triage GitHub PRs and issues using vision-based scoring.
Descrição
O que esta skill faz
Scores and prioritizes open GitHub pull requests against a project vision document. Three steps: onboard (interview the repo owner to define mission and rubric), scan (apply heuristic scoring to PRs), and report (generate markdown files grouped by priority tier). Duplicate detection and cron scheduling are included.
Scores PRs against a custom vision document derived from the actual repo owner's priorities, rather than applying generic quality heuristics.
Quando usá-la
- Triaging 50+ open PRs on a busy open source repo
- Building a priority queue before a release or milestone deadline
- Flagging spam and low-quality contributions automatically
- Detecting duplicate PRs across a large backlog
- Running weekly automated triage on a schedule
Exemplo de fluxo de trabalho
User asks: Triage the open PRs on github.com/myorg/myrepo
- 1
Run onboard.py with the repo URL to fetch README, CONTRIBUTING.md, and recent releases via gh CLI
- 2
Present interview questions to the repo owner covering mission, contribution priorities, and red/green flags
- 3
Save vision.md and rubric.md to the triage-config directory
- 4
Run scan.py against the repo using vision.md to score all open PRs and detect duplicates
- 5
Run report.py to produce prioritize.md, review.md, close.md, and summary.md
Four markdown reports grouping PRs by score tier (80+, 50-79, below 50), with a summary of score distribution, top PRs, duplicate candidates, and active authors
Requisitos
- gh CLI installed and authenticated via gh auth login
Instalação
clawhub install patrob/repo-pr-triageExecute o comando da CLI ou cole o prompt no Claude Code, Cursor, Codex ou no agente de código que você usa.