github-review-pr

1# Review a Contributor PR as Maintainer
2 
3Treat every verdict as a claim about exact immutable Git objects. Review each PR's
4prospective effect on the **current** base branch, not a stale web diff or an old
5review snapshot. A queue review is a sequence of independent PR reviews, never one
6shared approval or mutation batch.
7 
8Default to read-only. Do not comment, approve, request changes, update the branch,
9push, close, merge, enable auto-merge, bypass protections, or delete a branch unless
10the user explicitly authorizes that exact external mutation.
11 
12Use `$ARGUMENTS` as the target. Strip the recognized `--personal-maintainer` and
13`--all-open` flags before parsing it. If neither a PR nor an explicit all-open request
14can be resolved after inspecting the current repository and conversation, ask for the
15PR URL, `owner/repo#number`, or confirmation that all open PRs are in scope.
16 
17## Route the Request
18 
19Use this workflow for any of these:
20 
21- One open GitHub PR when the outcome is review, re-review, merge-readiness,
22  review-led repair, or review-led landing.
23- One explicitly named closed-unmerged PR when the user wants a retrospective merit
24  review, wants to know why it closed, or is considering whether it should stay closed
25  or be reopened. Reopening remains a separate mutation.
26- All currently open contributor PRs in one repository when the user explicitly asks
27  for an open-PR queue review. Process them by `createdAt` from newest to oldest and
28…