Batch Review PRs Awaiting Maintainer

This skill triages a batch of open pull requests end to end. It lists the candidate PRs, reviews each one, and then takes one of two actions per PR depending on whether the review surfaced any merge-blocker-level findings.

A finding is merge-blocker level when it is severe enough that the PR must not be merged as-is, typically severity high or critical (for example, correctness bugs, security vulnerabilities, data loss, or broken/failing CI). Findings of severity mid or low (style nits, minor refactors, non-urgent improvements) are not merge blockers.

Step 1: List Target PRs

Use the prs-awaiting-maintainer skill to list the open pull requests where the ball is in the maintainer's court, CI is green and the PR is ready to review, re-review, or merge. Collect their PR numbers as the work list for the following steps.

If the list is empty, report that there is nothing to triage and stop.

Step 2: Review and Resolve Each PR

Process the PRs one at a time. For each PR number target_pr:

2-1. Review

Use the review-pr skill with target_pr. It assigns each finding a severity (low / mid / high / critical) and also reports the GitHub Actions workflow status.

2-2. Classify

Decide whether the review produced any merge-blocker-level finding (severity high or critical, or failing/blocked CI), using the definition above.

2-3a. Has Merge-Blocker Findings → Post Comments

If there is at least one merge-blocker-level finding:

• Use the post-review-comments skill with target_pr, using the review results from Step 2-1 to leave line-level and overall review comments.
• Do not merge this PR. The ball goes back to the author.

2-3b. No Merge-Blocker Findings → Issue-ify and Merge

If there are no merge-blocker-level findings (only mid/low findings, or none at all):