skills.rest
dyoshikawa
dyoshikawaCOMMUNITY
Explore all skills by this author →
GitHub

prs-awaiting-author

Identify open pull requests requiring author intervention via GitHub CLI.

1|Updated Jun 25, 2026
Search Tags:#automation#code review#github#pull requests#developer productivity#ci-cd
One-click install
npx skills add https://github.com/dyoshikawa/webseek --skill prs-awaiting-author
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prs-awaiting-author
Source: https://github.com/dyoshikawa/webseek/tree/main/.rulesync/skills/prs-awaiting-author
Command: npx skills add https://github.com/dyoshikawa/webseek --skill prs-awaiting-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers and contributors quickly identify pull requests that are stalled because the author needs to address CI failures, review feedback, or unanswered questions.

Core Features & Use Cases

  • Actionable Filtering: Automatically distinguishes between PRs awaiting maintainer review and those requiring author intervention.
  • Signal Aggregation: Checks CI status, review decisions, and comment threads to determine the current state of a PR.
  • Use Case: A project lead can use this to generate a daily report of all open PRs that are currently blocked by the author, ensuring that contributors are prompted to resolve their pending tasks.

Quick Start

Run the prs-awaiting-author skill to list all open pull requests where the next action belongs to the author.

Frequently Asked Questions about prs-awaiting-author

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

FAQPage Schema
How do I find GitHub pull requests that are blocked waiting for the author to respond?▼

To find GitHub pull requests awaiting author action, you can analyze CI status, review decisions, and comment threads to distinguish stalled PRs from those needing maintainer review. This identifies open pull requests requiring author intervention to reduce cycle time.

Do I need the GitHub CLI installed to check which PRs require author intervention?▼

Yes, you need the GitHub CLI (gh) installed to query repository metadata and pull request activity. The GitHub CLI gathers the CI status, review decisions, and comment threads required to determine if a pull request is awaiting author intervention.

What is the best way to automate daily reporting of stalled pull requests?▼

The best way to automate daily reporting of stalled pull requests is to aggregate CI failures, review feedback, and unanswered questions. This actionable filtering generates a daily report of open pull requests currently blocked by the author.

Can this skill distinguish between PRs needing maintainer review and PRs needing author action?▼

Yes, it distinguishes between PRs awaiting maintainer review and those requiring author intervention. By checking CI status, review decisions, and comment threads, it applies actionable filtering to accurately determine the current state of a pull request.

What signals are used to determine if a pull request is awaiting author action?▼

The signals used to determine if a pull request is awaiting author action include CI status, review decisions, and comment threads. Aggregating these signals helps identify when a pull request is stalled because the author needs to address feedback or failures.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

GitHub Workflow

Manage GitHub issues, pull requests, releases, and repository status via gh CLI.

Community
Advanced
awais786awais786

sprint-report

Aggregate merged PRs, in-progress work, blockers, and completed issues into weekly sprint reports.

Community
Intermediate
bomberoxenviosdosruedasbomberoxenviosdosruedas

agency-devops-automator

Automate DevOps workflows with Terraform, GitHub Actions, Kubernetes, and Prometheus.

Community
Advanced
aroidoaroido

command-sync-status

Aggregate Git status, GitHub Issues, and Pull Requests into a project summary.

Official
Intermediate