review-pr

Review GitHub pull requests with a phase-driven process and pending comments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many PR reviews are inconsistent, miss refactoring opportunities, and conflate existing discussion with independent analysis. This Skill enforces a reproducible, phase-driven review process that emphasizes simplification, questioning intent, and providing actionable feedback while preventing contamination from existing comments.

Core Features & Use Cases

  • Phase-driven workflow: explicit phases for gathering context, cloning the repo, running a refactoring-opportunities sub-agent, deep analysis, and a final preflight that reads existing review threads.
  • Deterministic repo inspection: instructs safe cloning into isolated temp directories and exact commands for fetching PR metadata and diffs to ensure reviews run against the real PR state.
  • Refactoring sub-agent & pending review generation: runs an automated refactor-opportunity analysis in parallel and incorporates high-maintenance suggestions as idea: comments in the pending review, ensuring all comments are prepared but not submitted.
  • Use Case: a reviewer or automated assistant who must produce consistent, high-quality reviews across many repositories without accidentally submitting or contaminating threads.

Quick Start

Review PR 196 in owner/repo and produce a pending review scaffold following Thomas's Phase 1–7 process without submitting any 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 GitHub PR reviews to find refactoring opportunities?

Automating GitHub PR reviews involves cloning the repository, inspecting diffs locally, and running a refactoring-opportunities analysis to generate high-signal, actionable feedback without submitting comments.

What is the best way to prevent existing review comments from influencing a new PR analysis?

To prevent existing comments from influencing PR analysis, defer reading existing review threads until a final preflight phase, ensuring your independent inspection of diffs and files remains uncontaminated by prior discussion.

How do I prepare a pending GitHub code review without submitting it?

Preparing a pending GitHub code review requires gathering PR metadata, running deep analysis, and generating a structured checklist with comments locally, holding the final review in a pending state without submitting it to the repository.

Does this automated PR review process work without submitting comments to GitHub?

Yes, this automated PR review process works by producing a comprehensive pending review scaffold with idea comments locally, explicitly avoiding any automated submission of comments or reviews to GitHub.

What is a phase-driven GitHub code review workflow?

A phase-driven GitHub code review workflow is a reproducible process that separates context gathering, deterministic repo inspection, refactoring analysis, and deep review generation into explicit sequential steps to ensure consistent, high-quality feedback.

How do I run a refactoring-opportunities analysis on a GitHub pull request?

Running a refactoring-opportunities analysis on a GitHub pull request requires cloning the repository into an isolated directory and deploying a background sub-agent to inspect files and surface high-maintenance suggestions as idea comments.