pr-review

Sync branches, diff changes, and generate structured GitHub PR review documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates local PR reviews by syncing your environment with the PR branch, diffing changes, and consolidating developer notes into a single, structured review document.

Core Features & Use Cases

  • Syncs the local workspace with the PR branch and generates a comprehensive diff.
  • Audits changes against project conventions and extracts TODOs or follow-ups from the PR description and comments.
  • Outputs a structured review doc to blocks/{blockname}/pr-{PR_NUMBER}-review.md when reviewing a block, or to docs/pr-reviews/pr-{PR_NUMBER}-review.md for non-block changes.

Quick Start

Provide the PR number to review and run the pr-review skill to generate a structured review document.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate local code reviews for GitHub pull requests?

To automate local code reviews, this Skill syncs your workspace with the PR branch, generates a diff, and consolidates developer notes into a single structured review markdown document for offline preparation.

Can I review GitHub PR changes offline without a direct internet connection?

Yes, you can review GitHub PR changes offline. The Skill syncs the PR branch to your local environment first, enabling you to perform offline review and catch pre-merge issues without active internet access.

Do I need the gh CLI to generate a structured PR review document?

You need the gh CLI for authentication to generate a structured PR review document, but the Skill includes a fallback to standard git commands if gh CLI is not available or authenticated in your local dev environment.

Where are the structured markdown files saved after a local PR review?

The structured markdown files are saved locally after a PR review. Output goes to blocks/{blockname}/pr-{PR_NUMBER}-review.md for block changes, or docs/pr-reviews/pr-{PR_NUMBER}-review.md for non-block changes.

What is the best way to extract TODOs and check conformance during a PR diff?

The best way to extract TODOs and check conformance during a PR diff is using this Skill, which audits changes against project conventions and extracts follow-ups from the PR description and comments automatically.

Can I use this PR review automation for non-block repository changes?

Yes, you can use this PR review automation for non-block repository changes. The Skill handles any open GitHub PR and outputs the structured review document to the docs/pr-reviews/ directory.