prs-awaiting-maintainer

Identify open pull requests requiring maintainer intervention via GitHub CLI.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/dyoshikawa/webseek --skill prs-awaiting-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prs-awaiting-maintainer
Source: https://github.com/dyoshikawa/webseek/tree/main/.rulesync/skills/prs-awaiting-maintainer
Command: npx skills add https://github.com/dyoshikawa/webseek --skill prs-awaiting-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the bottleneck of identifying which pull requests are ready for maintainer attention, preventing PRs from stalling due to lack of visibility.

Core Features & Use Cases

  • Automated Triage: Filters open, non-draft PRs to find those with passing CI and pending maintainer action.
  • Contextual Analysis: Distinguishes between author-blocked and maintainer-blocked PRs by analyzing review history and commit timelines.
  • Use Case: A maintainer can quickly generate a prioritized list of PRs that are ready to be merged or reviewed, ensuring that active contributions are not overlooked.

Quick Start

Run the prs-awaiting-maintainer skill to generate a report of all open pull requests currently requiring your review or merge action.

Frequently Asked Questions about prs-awaiting-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify which GitHub pull requests need maintainer review?

To identify pull requests needing maintainer review, you filter open non-draft PRs by analyzing CI status, review history, and author activity. This process isolates PRs with passing CI and pending maintainer action, distinguishing them from author-blocked contributions.

What is the best way to automate PR triage for stalling code reviews?

Automating PR triage for stalling code reviews involves querying repository metadata to evaluate PR state transitions. By distinguishing between author-blocked and maintainer-blocked PRs through commit timelines, you prevent active contributions from being overlooked.

Does automated pull request triage work with GitHub CLI?

Yes, automated pull request triage works with GitHub CLI integration to query repository metadata. It requires this integration to evaluate CI status, review history, and author activity, determining which PRs are ready for maintainer intervention.

Why do my GitHub pull requests keep stalling before merge?

Your GitHub pull requests may stall due to a lack of visibility into which PRs actually require maintainer attention. PRs often stall when bottlenecks occur because passing CI and pending reviews are not clearly prioritized for maintainer action.

How do I distinguish author-blocked PRs from maintainer-blocked ones?

To distinguish author-blocked from maintainer-blocked PRs, analyze the review history and commit timelines. This contextual analysis determines whether the delay is caused by the author's inactivity or a pending maintainer review or merge action.

When should I exclude draft PRs from code review triage?

You should exclude draft PRs from code review triage when filtering for open pull requests that are ready for maintainer intervention. Draft PRs indicate work in progress and should be omitted to ensure only actionable, review-ready contributions are prioritized.