review-github-pr

Summarize GitHub pull request diffs and identify key design decisions.

8.1k|1.2k|Updated Feb 24, 2026

Search Tags:#github #review #diff #code-review #pull-request #design-decisions

Ready to run

npx skills add https://github.com/NVIDIA/OpenShell --skill review-github-pr-nvidia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-github-pr
Source: https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/review-github-pr
Command: npx skills add https://github.com/NVIDIA/OpenShell --skill review-github-pr-nvidia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly understand and evaluate GitHub pull requests by producing a concise summary of the diff and the critical design decisions, saving time during code reviews.

Core Features & Use Cases

Summarizes PR diffs to highlight changes, rationale, and potential impacts.
Identifies key design decisions, references, and notable code snippets for quick review.
Uses PR metadata (title, author, branches) to provide context and assist in branch- or PR-focused workflows.

Quick Start

Provide a PR number or a branch name to generate a review summary.

Frequently Asked Questions about review-github-pr

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

FAQPage Schema

How do I summarize a GitHub pull request diff for code review?▼

To summarize a GitHub pull request diff for code review, provide a PR number or branch name to generate a focused review highlighting key changes and design decisions. The tool requires authenticated gh CLI access and a valid git repository with a GitHub remote to fetch titles, bodies, and diffs.

What's the best way to identify key design decisions in a GitHub diff?▼

The best way to identify key design decisions in a GitHub diff is to use an automated code review summarizer that analyzes PR metadata alongside the diff. This highlights rationale, references, and notable code snippets to save time during manual evaluation.

Do I need the gh CLI installed to review pull requests by branch name?▼

Yes, you need the authenticated gh CLI installed to review pull requests by branch name. The tool also requires a valid git repository with a configured GitHub remote to successfully access and fetch the necessary PR data.

Can I use pull request metadata to provide context for branch-focused workflows?▼

Yes, you can use pull request metadata like titles, authors, and branches to provide context for branch-focused workflows. The summarizer extracts this metadata alongside the diff to evaluate changes and assist in targeted PR-focused tasks.

Why does my pull request review fail to fetch the diff data?▼

Your pull request review fails to fetch diff data if the gh CLI is not authenticated or if the current directory is not a valid git repository with a GitHub remote. Ensure both prerequisites are met to access PR titles, bodies, and diffs.