pr-review-guide

Review pull requests against project rules and produce structured verdicts with inline comments.

1|1|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/nexuslabs-ai/nexus --skill pr-review-guide-nexuslabs-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review-guide
Source: https://github.com/nexuslabs-ai/nexus/tree/main/.agents/skills/pr-review-guide
Command: npx skills add https://github.com/nexuslabs-ai/nexus --skill pr-review-guide-nexuslabs-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request reviews are often inconsistent, miss third-party API misuse, or bury findings in verbose prose. This Skill enforces a repeatable review process that checks diffs against project conventions, mandates external technology research, and returns findings in a strict structured format. ## Core Features & Use Cases - Rule-based diff checking: Loads project rule files (guard clauses, ripple effects, code comments, no-follow-up-deferral) and flags violations with file:line references. - Mandatory dependency research: Requires web research on every third-party library used in the diff to verify correct usage, version-specific behavior, and common mistakes. - Structured output with caps: Returns a verdict (APPROVED / COMMENT / CHANGES REQUIRED), an issues table, optional architectural concerns, and inline comments with strict word limits. - Use Case: A reviewer asks the agent to evaluate PR #142 touching React components; the Skill reads the diff via gh, verifies Radix UI usage against current docs, and returns blocking and minor findings ready for the caller to post. ## Quick Start Review pull request 142 for code quality and architecture, then return the structured review body, inline comments, and verdict.

Frequently Asked Questions about pr-review-guide

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

FAQPage Schema
How do I review a pull request with an AI agent?▼

Invoke the review on a PR number; the agent reads the description and diff via gh, checks changes against project rule files, researches third-party dependencies, and returns a structured review body with inline comments and a verdict for the caller to post.

What does the PR review check for in code changes?▼

It checks diffs against rules covering guard clauses, ripple effects, composition patterns, useEffect misuse, logging proportionality, code comments, and follow-up deferral. It also flags exposed secrets, leftover debug code, and out-of-scope changes.

Does the review verify third-party library usage?▼

Yes, external technology research is mandatory for any PR using third-party dependencies. The reviewer searches for correct usage, configuration options, common mistakes, and version-specific behavior, then reports findings in a Research Flags section.

Can the review post comments directly to GitHub?▼

No, the Skill explicitly does not post reviews itself. It returns a structured payload with the review body, inline comments with file paths and line numbers, and a verdict, which the calling command is responsible for posting.

What verdicts can a pull request review return?▼

Verdicts depend on the reviewing agent: Principal Architect returns APPROVED, NEEDS DISCUSSION, or CHANGES REQUIRED; SDE2 returns APPROVED, MINOR CHANGES, or CHANGES REQUIRED. Bugs and architectural issues force CHANGES REQUIRED.