Agent skill · Code Review & Quality

prs-awaiting-author

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.

dyoshikawa1,265★ · +16/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add dyoshikawa/rulesync --skill prs-awaiting-author --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 3 KB
Bundled scripts: none
Path: .rulesync/skills/prs-awaiting-author/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,285 · +20 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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

What's inside
Steps it walks through
  1. Signals That the Ball Is on the Author's Side
  2. Step 1: List Open PRs
  3. Step 2: Gather Per-PR Signals
  4. Step 3: Classify
  5. Step 4: Report
Commands it runs
gh pr list --state open --limit 100 --json number,title,author,isDraft,createdAt,updatedAt,url,reviewDecision,reviewRequests
More from rulesync
All skills →
About this skill
What does the prs-awaiting-author skill do?

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.

How do I install it?

Run `npx skills add dyoshikawa/rulesync --skill prs-awaiting-author --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going