review-pr

Automate single-pass GitHub PR reviews with inline comments and reasoning.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/DominionZA2/claude-config --skill review-pr-dominionza2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/DominionZA2/claude-config/tree/main/skills/review-pr
Command: npx skills add https://github.com/DominionZA2/claude-config --skill review-pr-dominionza2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured single-pass PR code reviews require capturing every observation as a public comment with reasoning so nothing is re-discovered in a future session. This skill automates the end-to-end process, producing a consistent, durable record on the PR itself and preventing restart work.

Core Features & Use Cases

  • Pre-flight restart protection to detect prior reviews and scope changes.
  • Ingest existing discussion across inline comments, PR-level notes, and reviews to avoid re-flagging anchors.
  • Systematic diff reading with surrounding context to identify real findings, nitpits, and pre-existing issues.
  • Templates for real findings, pre-existing observations, and verified-correct checks to keep reviews clear and repeatable.
  • Auto-generate inline comments on the PR and PR-level comments for meta-notes, with commit-traceability practices.

Quick Start

Provide a PR number or URL to generate a complete one-pass review with inline and PR-level comments.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate a single-pass GitHub pull request code review?

To automate a single-pass GitHub pull request code review, provide a PR number or URL and the skill reads PR metadata, diffs, and discussion history via gh pr view and gh pr diff to generate structured inline comments with reasoning.

What is the best way to avoid re-flagging existing comments during a PR review?

The best way to avoid re-flagging existing comments during a PR review is to ingest prior discussions across inline comments and PR-level notes before analysis, ensuring previously identified anchors are skipped and preventing duplicate review work.

Can I use this to review a pull request that has already been partially reviewed?

Yes, you can review a pull request that has been partially reviewed because the skill applies pre-flight restart protection to detect prior reviews and scope changes, preserving durable context to prevent restarting the code review process.

How does structured code review handle pre-existing issues found in a PR diff?

Structured code review handles pre-existing issues found in a PR diff by categorizing them using dedicated templates for pre-existing observations, separating them from real findings and nitpicks to keep the review clear and repeatable.

Do I need the GitHub CLI installed to perform automated code reviews?

Yes, you need the GitHub CLI installed to perform automated code reviews because the skill requires reading PR details and diffs via gh pr view <num> and gh pr diff <num> commands to analyze the pull request.

Why should I use templates for pull request code reviews?

You should use templates for pull request code reviews to classify findings, anchor observations to the PR, and maintain a consistent, durable record with commit-traceability, preventing scope creep and preserving reasoning for future sessions.