review

Analyze branch, PR, or working tree diffs into markdown reports.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/jwadhwa2259/codescope --skill review-jwadhwa2259
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/jwadhwa2259/codescope/tree/main/skills/review
Command: npx skills add https://github.com/jwadhwa2259/codescope --skill review-jwadhwa2259

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze a branch, PR, or working tree diff to surface structural impact, risk zones, and blast radius, delivering a concise, readable report for faster, safer code reviews.

Core Features & Use Cases

  • Impact analysis of changes before merging to understand ripple effects across the codebase.
  • Risk scoring that highlights high-impact files and critical dependencies to prioritize review.
  • Automated reporting that formats findings into a readable markdown summary for teammates and stakeholders.

Quick Start

Provide a PR number, a branch name, or leave empty to analyze the working tree diff and produce a report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I analyze a pull request for structural impact and risk zones?

To analyze a pull request for structural impact and risk zones, provide the PR number to generate a concise markdown report highlighting ripple effects, blast radius, and high-risk files for code review.

Can I review code quality by analyzing a branch diff before merging?

You can review code quality by analyzing a branch diff before merging to surface structural impact, risk scoring, and critical dependencies, delivering a readable markdown summary to guide review focus and risk mitigation.

What is blast radius analysis in a code review?

Blast radius analysis in a code review identifies the structural impact and ripple effects of changes across a codebase, helping reviewers understand how modifications to specific files affect critical dependencies before merging.

Do I need any external dependencies to perform risk analysis on a working tree diff?

No external dependencies are required to perform risk analysis on a working tree diff, as the tool operates independently by calling the codescope_review MCP tool to format the JSON response into a markdown report.

What's the best way to prioritize code review focus for high-impact files?

The best way to prioritize code review focus for high-impact files is to apply risk scoring to a pull request or branch diff, which highlights critical dependencies and structural impact to guide risk mitigation efforts.