pr-triage
Installation
SKILL.md
PR triage
Tell the user which open PRs need them, and why, then help them act. Uses the gh CLI. Works on GitHub and GitHub Enterprise: don't hardcode a host.
Two kinds of PR:
- A. Needs your action: the user already reviewed it and it has changed (or they were asked to review it again).
- B. Needs your review: the user hasn't reviewed it, and they were asked to, or it matches their skill set.
Rules
- Everything here is a draft for the user to verify. Say which commits or files you did not read in detail.
- Never write to a PR (approve, comment, request changes, dismiss) without the user's explicit answer for that PR. Show the exact text first.
- Always show the change summary (step 5) before asking what to do with an A PR. No size threshold: small changes can change a PR's meaning, so don't skip or pre-select an option because a change looks small.
- Skip the user's own PRs and drafts.
- Never approve a B PR: the user hasn't reviewed it. Offer a full review instead.