# Prs Awaiting Author

List open pull requests where the ball is in the author's court: CI is failing, review...

- Repository: https://github.com/dyoshikawa/rulesync (1577 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add dyoshikawa/rulesync --skill prs-awaiting-author -g -a claude-code -y`
Codex: `npx skills add dyoshikawa/rulesync --skill prs-awaiting-author -g -a codex -y`
Cursor: `npx skills add dyoshikawa/rulesync --skill prs-awaiting-author -g -a cursor -y`
Gemini CLI: `npx skills add dyoshikawa/rulesync --skill prs-awaiting-author -g -a gemini-cli -y`

## Description

List open pull requests where the ball is in the author's court: CI is failing, review comments are unaddressed, or a maintainer question is awaiting the author's reply. Use when the user wants to see PRs awaiting author action.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# List PRs Awaiting Author Action

Identify open pull requests where the ball is in the **author's** court, the next action belongs to the PR author (fix CI, address review feedback, answer a question), not a maintainer.

## Signals That the Ball Is on the Author's Side

- CI is failing or has not been made to pass (failing or stuck checks).
- The latest review is `CHANGES_REQUESTED` and the author has not pushed follow-up commits since.
- There are review comments / inline threads the author has not yet replied to or resolved.
- A maintainer asked a question that is awaiting the author's reply.
- The PR is a draft (still work in progress on the author's side).

Exclude a PR when the next action clearly belongs to the maintainer (see the complementary `prs-awaiting-maintainer` skill): CI green, author has responded, and the PR is awaiting first review, re-review, or merge.

## Step 1: List Open PRs

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

Include drafts here, a draft is, by definition, still on the author's side.

## Step 2: Gather Per-PR Signals

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

- **CI status**: `gh pr checks <number>`, flag the PR if any check is failing.
- **Reviews and decision**: `gh pr view <number> --json reviewDecision,reviews,latestReviews`, flag if the decision is `CHANGES_REQUESTED`.
- **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, flag if a maintainer's comment or question is the most recent and remains unanswered.
- **Commit timeline vs. last review time**: to determine whether the author has pushed commits after a `CHANGES_REQUESTED` review (if not, the ball is still with the author).

The rest: https://github.com/dyoshikawa/rulesync/blob/HEAD/.rulesync/skills/prs-awaiting-author/SKILL.md