pr-round

Interprets GitHub pull request review bot signals and verdicts per commit.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/pdw96/ai-production-risk-early-warning --skill pr-round-pdw96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-round
Source: https://github.com/pdw96/ai-production-risk-early-warning/tree/main/.claude/skills/pr-round
Command: npx skills add https://github.com/pdw96/ai-production-risk-early-warning --skill pr-round-pdw96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Review bots like Codex and CodeRabbit leave ambiguous signals on GitHub pull requests—reactions, empty review arrays, and comments—that are easy to misread as a clean verdict. This Skill teaches how to correctly read one PR review round so an unreviewed commit is never mistaken for an approved one. ## Core Features & Use Cases - Signal interpretation: Distinguishes the three clean-round signals (review submission, no-finding comment, thumbs-up reaction) and explains why an empty reviews array does not mean "not reviewed". - Commit-bound verdicts: Only counts a verdict when the bot-carried SHA (commit_id field or "Reviewed commit:" in the body) matches the current head SHA, never relying on timestamps or reactions. - Skip and nudge rules: Detects why a bot did not attach (bot-authored PR, fewer than 10 stars), when to wait versus escalate after 5 minutes of silence, and why only a human account may request a re-review. - Use Case: After pushing a fix to a stacked PR, an agent checks whether Codex actually reviewed the new head commit before reporting the round as clean to the author. ## Quick Start Read this Skill before opening a PR, marking it ready, or interpreting Codex or CodeRabbit review results on any pull request in this repository.

Frequently Asked Questions about pr-round

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

FAQPage Schema
How do I verify a Codex review covered the latest commit?

Check that the review's commit_id field, or the "Reviewed commit: <sha>" line in a no-finding comment body, equals the PR's current head.sha from GET /pulls/N. Reactions carry no commit, so a thumbs-up alone is a signal, not a verdict.

Why is the GitHub reviews array empty when the PR was reviewed?

When Codex finds no issues it may leave only a thumbs-up reaction or a plain comment instead of submitting a review, leaving the reviews array empty. An empty array means no review object exists, not that nobody looked.

Why did the review bot not attach to my pull request?

Common reasons are a bot-authored PR ("Review skipped — Bot user detected") or a repository with fewer than 10 stars, which disables automatic reviews. Read the skip message; a human marking it ready or triggering review manually resolves it.

When should I re-request a review after marking a PR ready?

If no reaction or review appears within 5 minutes of the ready transition, escalate to the author. Do not nudge if the bot's eyes reaction is already present, and note that only a human account can post the re-review request.

Can a thumbs-up reaction confirm my code was approved?

No. Reactions carry no commit SHA and no start time, so they cannot be bound to any specific commit. Treat them as unverifiable signals and report them as "confirmation unavailable" rather than a clean verdict.