pr-review

Analyze local pull request diffs and generate structured code review reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mitchlabeetch/Largarda --skill pr-review-mitchlabeetch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/mitchlabeetch/Largarda/tree/main/.agents/skills/pr-review
Command: npx skills add https://github.com/mitchlabeetch/Largarda --skill pr-review-mitchlabeetch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local PR review and validation with full project context, eliminating the need to rely on remote diffs or truncated CI data.

Core Features & Use Cases

  • Reads the PR diff and changed files from the local checkout, enabling accurate context even when remote data is limited.
  • Supports interactive and automated modes (with and without --automation) for flexible workflows.
  • Generates a detailed, structured code-review report and optional CI status summary to guide merges.
  • Suitable for pre-merge validation, knowledge transfer in teams, and offline code review workflows.

Quick Start

Provide a PR number to begin a local PR code 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 pull request locally with full project context?

Review a pull request locally by running the /pr-review command with a PR number. The tool orchestrates local git operations, fetches diffs, reads changed files, and runs lint to generate a structured code review report.

Can I automate code review for pre-merge validation?

Yes, you can automate code review for pre-merge validation using the --automation flag. This enables automated mode to validate changes and generate a CI status summary without interactive prompts.

What is the best way to analyze a PR diff without relying on remote data?

Analyzing a PR diff without remote data is best done by reading changed files directly from the local checkout. This approach ensures accurate context even when remote diffs or CI data are truncated.

Does local PR review run lint checks on changed files?

Yes, local PR review runs lint checks on changed files. It fetches the PR diff from your local git checkout, reads the modified files, and executes lint operations to include in the structured review report.

Can I use this for offline code review workflows?

Yes, you can use this for offline code review workflows. It reads PR diffs and changed files from the local checkout, enabling thorough review and knowledge transfer without depending on remote repository access.