review-pr

Name: review-pr
Availability: InStock
Author: toumakido

Analyze GitHub pull requests and generate structured Markdown review briefings.

Updated Nov 6, 2025

Search Tags:#performance #pull request #security #GitHub #code-review #analyze #test-coverage

Ready to run

npx skills add https://github.com/toumakido/my-claude --skill review-pr-toumakido

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review GitHub pull requests to help teams understand changes, assess impact, and decide on next steps without manually parsing diffs and comments.

Core Features & Use Cases

PR metadata analysis: Summarize author intent, changes scope, and risk level.
Diff-driven review: Inspect code changes with line-level impact and hotspots.
Comprehensive guidance: Provide actionable remediation steps, security considerations, and test coverage gaps.
Use Case: A maintainer can run this on a PR to generate a concise reviewer brief for fast triage.

Quick Start

Provide the PR number or URL to initiate the review process, and run from the repository root.

Frequently Asked Questions about review-pr

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

FAQPage Schema

How do I generate a comprehensive GitHub pull request review for code quality and security?▼

To generate a GitHub pull request review, run the skill from the repository root with the PR number. It analyzes diffs for code quality, security, performance, and test coverage, returning a structured Markdown brief with file:line references.

Can I automatically analyze test coverage gaps and security hotspots from a GitHub PR diff?▼

Yes, you can automatically analyze test coverage gaps and security hotspots from a PR diff. The skill fetches metadata and diffs via the gh CLI to inspect changes and provide actionable remediation steps for identified risks.

Does the GitHub PR review process require the gh CLI to fetch pull request data?▼

Yes, the GitHub PR review process requires the gh CLI to fetch pull request data. It uses gh pr view and gh pr diff commands in parallel to retrieve metadata and code changes needed for the comprehensive analysis.

What is the best way to triage GitHub pull requests for maintainers?▼

The best way to triage GitHub pull requests is to generate a concise reviewer brief. This skill summarizes author intent, change scope, and risk level, transforming diff-driven findings into a Markdown review ready for fast human consumption.

Do I need to provide a URL or just a PR number to initiate the automated code review?▼

You need to provide either the PR number or URL to initiate the automated code review. The skill operates from the repository root, using the provided reference to fetch the necessary pull request metadata and diffs.