review-pr

Analyze GitHub pull requests read-only and generate Markdown and JSON findings.

2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/FatBy/DD-OS --skill review-pr-fatby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/FatBy/DD-OS/tree/main/skills/agent-review-pr
Command: npx skills add https://github.com/FatBy/DD-OS --skill review-pr-fatby

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing GitHub pull requests, providing structured findings without altering the code.

Core Features & Use Cases

  • Read-only Analysis: Performs a comprehensive review of pull requests without making any modifications.
  • Structured Output: Generates both human-readable Markdown and machine-readable JSON reports of findings.
  • Deterministic Review: Leverages scripts for consistent and repeatable review processes.
  • Use Case: A developer needs to quickly assess a pull request for potential issues before it's merged. This Skill can be used to generate a detailed review report, flagging any concerns and ensuring code quality.

Quick Start

Use the review-pr skill to analyze pull request number 123.

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 pull request analysis to generate structured code review reports?

Automate GitHub pull request analysis by running shell scripts to perform read-only code reviews. This process generates deterministic findings in both Markdown and JSON formats for handoff to subsequent preparation stages.

Can I use shell scripts for deterministic code review without modifying the repository?

Yes, you can use shell scripts for deterministic code review without modifying the repository. The process performs read-only GitHub pull request analysis and enforces guardrails to ensure safety and accuracy.

What is the best way to extract JSON and Markdown findings from a pull request review?

The best way to extract JSON and Markdown findings is to use a script-first PR review process. It automates read-only GitHub pull request analysis and outputs structured findings for both human readability and machine processing.

Does automated pull request analysis require explicit branch mode switching?

Yes, automated pull request analysis requires explicit branch mode switching. This ensures deterministic code review by validating artifacts and enforcing guardrails throughout the read-only GitHub analysis process.

How do I flag potential issues in a pull request before merging?

Flag potential issues in a pull request before merging by running automated read-only analysis scripts. This generates a detailed review report with structured findings in Markdown and JSON formats to ensure code quality.