differential-review

Generate Markdown audit reports from security-focused differential code review.

2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/roderik/mpe --skill differential-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: differential-review
Source: https://github.com/roderik/mpe/tree/main/.agents/skills/differential-review
Command: npx skills add https://github.com/roderik/mpe --skill differential-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates security-focused differential review of code changes (PRs, commits, diffs), ensuring issues are surfaced with context, evidence, and actionable steps.

Core Features & Use Cases

  • Phase-aware analysis: Adapts depth to codebase size and risk, using git history for context.
  • Blast radius & test coverage: Calculates blast radius and checks test coverage to prioritize fixes.
  • Automated reporting: Generates comprehensive Markdown audit reports and supports integration with issue-writer workflows.
  • Use Case: Review a mid-size PR to produce a structured report highlighting HIGH-risk changes and potential regressions.

Quick Start

Use this skill on a PR diff to generate a differential review report with risk-guided remediation.

Frequently Asked Questions about differential-review

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

FAQPage Schema
What is blast radius analysis in differential code review?

Blast radius analysis in differential review calculates the potential impact of code changes across the codebase. By combining this with test coverage checks, the review prioritizes fixes for high-risk regressions before producing a comprehensive audit report.

Does automated differential review work on individual commits and diffs?

Automated differential review works across PRs, individual commits, and standard diffs. It leverages git history to provide phase-aware context and adapts its analysis depth to varying codebase sizes and team workflows.

Can I generate compliance audit reports from git history and test coverage analysis?

You can generate compliance audit reports by running security-focused differential review on code changes. The process produces comprehensive Markdown audit reports containing evidence and actionable steps suitable for stakeholder review and compliance records.

What is the best way to find high-risk regressions in a mid-size PR?

The best way to find high-risk regressions is using phase-aware differential review that calculates blast radius and checks test coverage. This approach surfaces structural issues with context and evidence, outputting a structured report for remediation.

Are there limitations when reviewing large codebase diffs without test coverage?

Reviewing large codebase diffs without test coverage limits the ability to prioritize fixes accurately. The analysis relies on blast radius and test coverage checks to adapt depth and assess risk, meaning missing coverage reduces the precision of regression detection.