review-pr

Review GitHub pull requests and post structured comments with merge verdicts.

8|5|Updated Feb 18, 2026

Search Tags:#diff analysis #code review #pull request #github #risk assessment #merge readiness #automated comments

Ready to run

npx skills add https://github.com/shenxingy/Clade --skill review-pr-shenxingy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/shenxingy/Clade/tree/main/configs/skills/review-pr
Command: npx skills add https://github.com/shenxingy/Clade --skill review-pr-shenxingy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams save time and reduce review cycles by converting a raw pull request diff into a structured, consistent review comment.

Core Features & Use Cases

Structured review output: Produces a concise summary, key changes by file, identified risks, and targeted suggestions when applicable.
Supports PR selection: Review the current branch, a PR number, or a full PR URL.
Auto-posts to GitHub: Publishes the review as a PR comment using gh, ready for team discussion.
Use case: When preparing a PR for merge, it helps maintainers quickly spot risky changes and missing considerations (e.g., behavior changes, edge cases, or refactor side effects) before code lands.

Quick Start

Ask the AI to run the review on a specific pull request by using /review-pr 42.

Frequently Asked Questions about review-pr

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

FAQPage Schema

How do I generate an automated code review for a GitHub pull request?▼

To generate an automated code review for a GitHub pull request, use the review-pr Skill to read the PR diff and post a structured comment. It analyzes the diff deterministically and publishes a formatted summary of changes, risks, and a merge verdict directly to GitHub.

Can I post structured pull request comments using a PR number or URL?▼

Yes, you can post structured pull request comments by providing a specific PR number, full URL, or current branch name. The Skill invokes gh to resolve the target pull request, fetch the necessary diff metadata, and auto-post the generated review comment to that exact PR.

What is included in an automated pull request risk assessment?▼

An automated pull request risk assessment includes a concise summary, key changes organized by file, and identified risks like behavior changes or refactor side effects. It also provides targeted suggestions and a final merge verdict to help maintainers spot missing considerations.

Do I need the GitHub CLI installed to analyze PR diffs and post comments?▼

Yes, you need the GitHub CLI installed because the Skill requires invoking gh to resolve pull requests and fetch diffs. It relies on the gh tool to retrieve the PR context and auto-post the structured review comment back to the correct GitHub repository.

How do I review code changes on my current branch before merging?▼

To review code changes on your current branch before merging, run the review-pr Skill without specifying a PR number. It automatically detects the current branch, resolves the associated pull request, fetches the diff, and posts a structured review comment to help spot risky changes.

Are there size limitations when analyzing large pull request diffs?▼

Yes, there are size limitations when analyzing large pull request diffs because the Skill analyzes content deterministically within size constraints. Extremely large diffs may exceed these processing limits, so it is best suited for standard-sized pull requests to ensure a complete and structured review.