List PRs Awaiting Maintainer Action

Identify open pull requests where the ball is in the maintainer's court, the PR is ready and the next action belongs to a maintainer (review, re-review, or merge), not the author.

Signals That the Ball Is on the Maintainer's Side

• CI is fully green: every check is passing, with none failing or pending.
• The PR is not a draft.
• And at least one of:
  • The PR was newly opened and has not been reviewed yet (awaiting first review).
  • The author pushed new commits after a CHANGES_REQUESTED review (re-review needed).
  • The author has replied to or resolved the review comments and is now waiting on the maintainer.
  • A maintainer review was requested and has not yet been provided.
• The most recent meaningful activity is from the author (or CI), not an unanswered maintainer question.

Exclude a PR when the next action clearly belongs to the author (see the complementary prs-awaiting-author skill): CI failing, unaddressed review comments, changes requested without follow-up commits, or an open maintainer question awaiting the author's reply.

Step 1: List Open Non-Draft PRs

gh pr list --state open --limit 100 --json number,title,author,isDraft,createdAt,updatedAt,url,reviewDecision,reviewRequests

Skip any PR where isDraft is true.

Step 2: Gather Per-PR Signals

For each candidate PR, gather details (run in parallel across PRs where practical):

• CI status: gh pr checks <number>, treat as green only if every check is passing and none are pending or failing.
• Reviews and decision: gh pr view <number> --json reviewDecision,reviews,latestReviews,reviewRequests.
• Discussion and who spoke last: gh pr view <number> --comments, and if needed gh api repos/{owner}/{repo}/pulls/<number>/comments for inline review threads.
• Commit timeline vs. last review time: to determine whether the author pushed commits after a CHANGES_REQUESTED review.