review-pr

Name: review-pr
Availability: InStock
Author: jonnytacos8

Analyze a GitHub pull request and write a structured A-J review to .local/review.md.

Updated Feb 13, 2026

Search Tags:#automation #safety #review #code-review #pull-request #gh-cli

Ready to run

npx skills add https://github.com/jonnytacos8/closed_claw --skill review-pr-jonnytacos8

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/jonnytacos8/closed_claw/tree/main/.agents/archive/review-pr-v1
Command: npx skills add https://github.com/jonnytacos8/closed_claw --skill review-pr-jonnytacos8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, read-only PR review workflow that helps reviewers generate actionable feedback without pushing changes or merging.

Core Features & Use Cases

Structured A-J style review format with goals, risks, tests, and documentation checks.
Safe, deterministic guidance using the gh CLI and local artifacts, ensuring no code changes are made.
Use case: a reviewer receives a PR and needs a concise, production-ready assessment to decide on next steps.

Quick Start

Analyze a PR and generate a thorough review using gh CLI, then save outputs to .local/review.md and .local/pr-meta.env.

Frequently Asked Questions about review-pr

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

FAQPage Schema

How do I generate a structured code review for a GitHub pull request without merging it?▼

Generate a read-only pull request review by analyzing the PR using the gh CLI, producing a multi-section assessment with risks, tests, and documentation gaps. Outputs are saved to .local/review.md and .local/pr-meta.env without making any code changes or merging.

Can I automate pull request safety checks to ensure no code modifications are made during the review?▼

Yes, automated PR safety checks can be performed using deterministic gh CLI guidance. The process ensures a read-only assessment, generating structured feedback and metadata without pushing changes or merging the branch.

What is the best way to analyze a GitHub PR for documentation gaps and missing tests?▼

Analyzing a GitHub PR for documentation gaps and missing tests involves generating a structured A-J style review. This assessment covers goals, risks, tests, and documentation checks, saving the production-ready feedback to a local markdown file.

Does the gh CLI support extracting PR metadata for a local code review workflow?▼

Yes, the gh CLI supports extracting PR metadata for a local code review workflow. The Skill uses it to gather pull request details and outputs the metadata to a .local/pr-meta.env file for seamless handoff.

Do I need any external dependencies to perform an automated code review on a GitHub pull request?▼

No external dependencies are required to perform this automated code review. The Skill operates using the gh CLI and local artifacts to safely analyze the pull request and generate the structured review files.

Why use a read-only PR review workflow instead of directly modifying the codebase?▼

A read-only PR review workflow ensures safe, deterministic guidance by preventing accidental code changes. It helps reviewers generate actionable feedback and decide on next steps without the risk of merging or pushing unintended modifications.