pr-review-churn
Installation
SKILL.md
PR Review Churn
Overview
Analyze authored pull requests with thread-aware GitHub review data, identify repeated reviewer objection patterns, and return a read-only report with proposed workflow improvements. Do not post GitHub comments, edit repositories, or change skills/policy files unless the user explicitly asks for a follow-up implementation.
Scope
- Repositories and lookback have no defaults. Use the user's explicit scope from this conversation; ask for any missing values together, such as: "Which repositories (
owner/repo), and how many days back should I analyze?" Wait for the answer before collecting PR data. Do not infer scope from the current checkout or a previous report. - Author: infer the current GitHub login with
gh api user --jq .loginwhen the user does not specify one - Evidence: prefer GitHub GraphQL
reviewThreads; flat PR comments are fallback context only - The bundled collector selects PRs created on or after a UTC cutoff date, then fetches their review threads. It does not select reviews submitted during that period on older PRs. State this cohort in the report; a request for review activity in an exact date range needs different collection/filtering before making that claim.
Read references/report-guidance.md before synthesizing findings.