batch-review-prs-awaiting-maintainer
Batch-triage open pull requests: list PRs with prs-awaiting-maintainer, review each with review-pr, then post-review-comments when there are merge-blocker findings, or create-scrap-issue for non-blocking findings and merge-pr when there are none. Use when the user wants to review and resolve a batch of PRs in one pass.
Profile →npx skills add dyoshikawa/rulesync --skill batch-review-prs-awaiting-maintainer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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`) an
- Step 1: List Target PRs
- Step 2: Review and Resolve Each PR
- 2-1. Review
- 2-2. Classify
- 2-3a. Has Merge-Blocker Findings → Post Comments
- 2-3b. No Merge-Blocker Findings → Issue-ify and Merge
- Step 3: Final Report
What does the batch-review-prs-awaiting-maintainer skill do?
Batch-triage open pull requests: list PRs with prs-awaiting-maintainer, review each with review-pr, then post-review-comments when there are merge-blocker findings, or create-scrap-issue for non-blocking findings and merge-pr when there are none. Use when the user wants to review and resolve a batch of PRs in one pass.
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill batch-review-prs-awaiting-maintainer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.