review-pr

Review GitHub pull requests read-only using gh CLI and git worktrees.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/RobbyMo81/assistantrobby --skill review-pr-robbymo81
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/RobbyMo81/assistantrobby/tree/main/.agents/archive/review-pr-v1
Command: npx skills add https://github.com/RobbyMo81/assistantrobby --skill review-pr-robbymo81

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a read-only, structured GitHub pull request review workflow that analyzes PR metadata, diffs, and files using the gh CLI and a local git worktree so reviewers can assess readiness without altering the repository.

Core Features & Use Cases

  • Isolated worktree review: fetch PR refs, inspect diffs, and browse PR versions in an isolated worktree to avoid touching main branches.
  • Structured deliverables: produces a TODO checklist, saves PR metadata to .local/pr-meta.env, and writes a full structured review to .local/review.md with sections A through J.
  • Safety-first guardrails: explicit rules forbid pushing, merging, killing gateway processes, or running destructive commands during review. Use case: evaluate a feature PR for correctness, tests, docs, and security before recommending prepare-pr actions.

Quick Start

Use the review-pr skill to perform a thorough, read-only review of PR 42 and save a structured review to the repository worktree.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I perform a read-only GitHub pull request review without merging changes?

You can perform a read-only GitHub pull request review by fetching PR refs into an isolated local git worktree using the gh CLI. This evaluates readiness, security, tests, and documentation while strictly forbidding pushes, merges, or destructive commands to keep the repository untouched.

What is the best way to review pull request diffs in an isolated environment?

Review pull request diffs in an isolated git worktree to avoid touching main branches. Fetch PR refs via the gh CLI into the worktree, inspect metadata and file changes locally, and generate a structured review document without pushing any modifications to the remote repository.

Do I need the gh CLI and git worktrees to review a pull request locally?

Yes, a local pull request review requires the gh CLI, git, and jq installed with a writable worktree and network access. These tools fetch PR refs and metadata so you can browse versions and produce structured deliverables without merging changes.

How does a structured pull request review assess code readiness and security?

A structured pull request review assesses code readiness and security by analyzing PR metadata and diffs to produce a comprehensive checklist. It writes a full structured review to review.md covering sections A through J, evaluating implementation correctness, tests, documentation, and security vulnerabilities.

What are the limitations of using a worktree for pull request reviews?

Limitations of using a worktree for pull request reviews include strict prohibitions against pushing, merging, killing gateway processes, or running destructive commands. The review is confined to read-only analysis, meaning you cannot apply fixes or prepare pull requests directly within this isolated workflow.