review-pr

Review GitHub pull requests via gh CLI and save findings to .local/review.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review-only GitHub pull request analysis with the gh CLI. Use when asked to review a PR, provide structured feedback, or assess readiness to land. Do not merge, push, or make code changes.

Core Features & Use Cases

  • Read PR meta and context with gh pr view to inform feedback.
  • Thoroughly compare PR diffs with gh pr diff and assess readiness to land.
  • Save structured findings to a local file for traceability and handoff.

Quick Start

Identify the PR you want to review, then run the workflow to generate a read-only assessment and save it to .local/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 perform a read-only GitHub pull request review using the gh CLI?

To review a GitHub pull request without merging or pushing changes, analyze the PR diff and description using gh pr view and gh pr diff. The workflow assesses readiness to land and saves structured findings to .local/review.md.

Can I assess PR readiness to land without modifying the repository?

You can assess PR readiness without modifying the repository by performing a strictly read-only code review. It analyzes diffs via gh CLI and saves findings locally, ensuring no pushes or merges occur.

What is the best way to generate structured code review feedback for a pull request?

The best way to generate structured code review feedback is to use a read-only gh CLI workflow. It checks if changes exist in main, analyzes the diff, and outputs findings to .local/review.md for handoff.

Does this pull request review workflow check if changes already exist in the main branch?

Yes, this pull request review workflow checks if changes already exist in main before analyzing the PR branch. It uses gh pr view to gather context and compares diffs to avoid redundant reviews.

How do I save pull request review findings locally for traceability?

To save pull request review findings locally for traceability, run a read-only gh CLI review process. It automatically writes structured assessment results and feedback into .local/review.md.