review-prep

Generate emergent and schema-driven diagrams with impact analysis for changed symbols.

2|1|Updated Oct 3, 2025
One-click install
npx skills add https://github.com/jamestexas/agents --skill review-prep-jamestexas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-prep
Source: https://github.com/jamestexas/agents/tree/main/skills/review-prep
Command: npx skills add https://github.com/jamestexas/agents --skill review-prep-jamestexas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews are time-consuming and error-prone; review-prep provides a local, structured context that shows what the PR proposes, what the code actually does, the gaps, and the blast radius of changed symbols.

Core Features & Use Cases

  • Synthesizes changed files from a pull request or diff into a focused scope for review.
  • Produces emergent and spec-driven diagrams when a mache schema is present, plus a targeted impact analysis for changed symbols.
  • Delivers a concise, reviewer-facing context that highlights gaps, drift, and potential blast radii to guide targeted testing and validation.

Quick Start

Analyze a PR by passing its number (e.g., 123) or owner/repo#N to generate the internal review context before posting a GitHub review.

Frequently Asked Questions about review-prep

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

FAQPage Schema
How do I generate impact analysis for changed symbols in a pull request?

To generate impact analysis for changed symbols in a pull request, identify changed files in the diff to determine the scope of impact. This process produces a targeted reviewer context highlighting blast radius and drift notes.

What is blast radius analysis in code review?

Blast radius analysis in code review identifies the scope of impact for changed symbols within a pull request. It generates a structured reviewer context that highlights drift notes and potential risks to guide targeted testing.

How do I prepare a structured PR review context before posting to GitHub?

Prepare a structured PR review context by passing a pull request number or owner/repo#N identifier. The system synthesizes changed files, diagrams, and impact analysis into a concise local context before you post a GitHub review.

Can I generate architecture diagrams from a diff automatically?

You can generate emergent architecture diagrams from a diff automatically. When a mache schema is present, the system also produces a schema-driven spec diagram to visualize the pull request changes.

Does review-prep require external dependencies to run local impact analysis?

Running local impact analysis requires no external dependencies. The tool synthesizes the pull request scope, diagrams, and blast radius internally to deliver a focused reviewer context without additional components.