Individual skill

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.

.rulesync/skills/batch-review-prs-awaiting-maintainer/SKILL.md

Read pinned source

Source commit 2d5bbc81aa01346601fcb2d1e18c71af07a02728

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,590
Repository last updated: Nov 7, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai Repository topic
ai-agents Repository topic
ai-coding Repository topic
llm Repository topic
mcp Repository topic
rules Repository topic
skills Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,409 bytes

Read excerpt


# 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