review-pr

Name: review-pr
Availability: InStock
Author: refined-prun

Review GitHub pull requests against project guidelines and produce a structured review artifact.

35|27|Updated Jul 6, 2024

Search Tags:#code review #linting #pull request #github #eslint #worktree #prettier

Ready to run

npx skills add https://github.com/refined-prun/refined-prun --skill review-pr-refined-prun

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, pnpm, and includes scripts (resource) components.

What problem does it solve?

This Skill reviews GitHub pull requests against repository rules and writes a structured review artifact so findings are consistent, traceable, and easy to resolve.

Core Features & Use Cases

PR Context Collection: Gathers PR metadata, diff output, and review comments for a complete review picture.
Automated Checks: Runs formatting and linting, then captures ESLint results for review decisions.
Isolated Analysis: Creates a detached worktree snapshot so the PR can be inspected without interference from local edits.
Use Case: Ask it to review a specific PR after a contributor update and produce .tmp/pr/number/pr-review.md with prioritized findings.

Quick Start

Review pull request 128 with the review-pr skill and write the findings to .tmp/pr/128/pr-review.md.

Frequently Asked Questions about review-pr

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

FAQPage Schema

How do I review a GitHub pull request against project guidelines?▼

To review a GitHub pull request, you collect PR metadata, diff output, and comments, then run formatting and linting checks to produce a structured review artifact with prioritized findings.

Can I run ESLint and Prettier checks on a PR without affecting my local changes?▼

Yes, you can run ESLint and Prettier checks on an isolated worktree snapshot, allowing you to inspect the pull request diff and verify formatting without interference from your local working directory edits.

What is the best way to generate a structured code review artifact for a GitHub PR?▼

The best way to generate a code review artifact is to evaluate the pull request diff against repository rules and output a traceable markdown file containing prioritized, structured findings for easy resolution.

Do I need pnpm and gh installed to review pull requests?▼

Yes, you need pnpm, gh, and git installed to review pull requests, because the process requires gathering PR metadata via gh, creating a git worktree, and running pnpm for linting and formatting verification.

Why use an isolated git worktree for pull request code review?▼

An isolated git worktree is used for pull request code review to create a detached snapshot, ensuring accurate diff-based analysis and preventing uncommitted local edits from interfering with linting and formatting checks.

What types of changes does a diff-based pull request review cover?▼

A diff-based pull request review covers code, documentation, styling, and tooling changes, applying repository-specific checks to generate a structured artifact for consistent and traceable findings.