pr-review

Review GitHub pull requests locally using metadata and diff context.

8|2|Updated Feb 2, 2021

Search Tags:#automation #github #metadata #review #diff #pull-request

Ready to run

npx skills add https://github.com/lhotari/pulsar-contributor-toolbox --skill pr-review-lhotari

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/lhotari/pulsar-contributor-toolbox/tree/main/claude-code/skills/pr-review
Command: npx skills add https://github.com/lhotari/pulsar-contributor-toolbox --skill pr-review-lhotari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review GitHub pull requests locally using both their metadata and diff as context, so you can assess intent, quality, and impact without posting comments on GitHub.

Core Features & Use Cases

PR metadata review: fetch title, body, labels, and author to understand the stated intent.
Diff-based validation: compare changes against the description to spot mismatches, gaps, and potential issues.
Output-focused analysis: present findings in the terminal with clear severity and guidance for next steps.

Quick Start

Provide a PR number (and optionally --repo owner/repo) to initiate a local PR review; optionally include --prompt to focus the review.

Frequently Asked Questions about pr-review

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

FAQPage Schema

How do I review a GitHub pull request locally without posting comments?▼

To review a GitHub pull request locally, you can fetch metadata and diffs using gh pr view and gh pr diff commands, analyzing intent and quality directly in your terminal without posting to GitHub.

What is the best way to validate pull request diffs against their metadata?▼

Validating pull request diffs against metadata involves comparing the code changes with the title, body, and labels to spot mismatches, gaps, and potential issues, producing a terminal-based analysis for the reviewer.

Can I focus my local PR review on specific security or compliance issues?▼

Yes, you can focus your local PR review on security or compliance issues by providing an optional focus prompt, directing the terminal-based analysis to validate specific concerns within the pull request diff.

Do I need to specify a repository to review a pull request from the terminal?▼

You do not always need to specify a repository to review a pull request; the tool supports parsing PR numbers and optional repository arguments, defaulting to the current local repository context when available.

What limitations exist when analyzing GitHub pull requests locally?▼

A limitation of analyzing GitHub pull requests locally is that the review is output-focused for the terminal only; it does not post comments or interact directly with GitHub issues, keeping the validation process strictly offline.