pr-review

Launch an Opus subagent to review a pull request and return a verdict.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jluckyiv/rivcomocktrial --skill pr-review-jluckyiv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/jluckyiv/rivcomocktrial/tree/main/.claude/skills/pr-review
Command: npx skills add https://github.com/jluckyiv/rivcomocktrial --skill pr-review-jluckyiv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures unbiased, rapid pre-merge PR reviews by spawning a fresh Opus subagent to read the pull request in isolation and return a concise verdict with precise file:line references.

Core Features & Use Cases

  • Independent review: A brand-new subagent reviews the PR without prior session context.
  • Clear verdicts: Merge, Fix first, or Hold, with actionable pointers to affected lines.
  • Traceability: Provides file:line references to locate issues quickly in the PR.
  • Use Case: Useful when a team wants a second pair of eyes on a branch before shipping.

Quick Start

Invoke with a PR number to launch a new Opus subagent that reviews that PR and returns a verdict.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I get an independent pull request review before merging?

To get an independent pull request review, you provide a PR number to spawn a fresh subagent. This subagent reads the code in isolation and returns a concise verdict of Merge, Fix first, or Hold.

What is an automated pre-merge PR review and how does it work?

An automated pre-merge PR review uses a fresh subagent to evaluate code changes without prior session context. It analyzes the pull request independently and returns a deterministic verdict with precise file:line references.

How do I run an independent code review on a single PR?

You run an independent code review by invoking the skill with a specific PR number. This launches a fresh Opus subagent to read the pull request and surface a structured verdict directly to the user.

Does the automated PR review provide specific file and line references?

Yes, the automated PR review provides specific file:line references for traceability. This allows developers to quickly locate issues identified by the subagent within the pull request diff.

Can I use a fresh subagent for code review without prior session context?

Yes, you can use a fresh subagent for code review to ensure an unbiased evaluation. The skill spawns a brand-new subagent specifically to read the pull request in isolation and return a clear verdict.

What are the limitations of using an automated subagent for PR review?

A limitation of automated subagent PR review is that it operates under a per-request flow and is applicable only to single-PR reviews. It does not carry broader session context across multiple evaluations.