differential-review

Performs security-focused differential review of code changes using git history and blast radius analysis.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/marumo333/atrox --skill differential-review-marumo333
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: differential-review
Source: https://github.com/marumo333/atrox/tree/main/.claude/skills/trailofbits/plugins/differential-review/skills/differential-review
Command: npx skills add https://github.com/marumo333/atrox --skill differential-review-marumo333

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Security regressions and vulnerabilities often slip through code review because reviewers lack historical context, miss transitive callers, or underestimate small changes. This Skill systematically analyzes PRs, commits, and diffs to detect security regressions, missing validation, and access control bypasses before merge. ## Core Features & Use Cases - Risk-Adaptive Analysis: Classifies changes by risk level (HIGH/MEDIUM/LOW) and scales review depth to codebase size (SMALL/MEDIUM/LARGE). - Git History & Blast Radius: Uses git blame to detect regressions of previous security fixes and quantifies caller impact for prioritization. - Adversarial Modeling & Reporting: Builds concrete exploit scenarios with exploitability ratings and generates comprehensive markdown reports with severity tables and recommendations. - Use Case: Reviewing a smart contract PR that removes a require check, the Skill traces the check's origin via git blame, finds it was added for a CVE fix, models an exploit scenario, and flags it as a CRITICAL regression in the report. ## Quick Start Ask the AI to perform a differential security review of the current PR or commit range and generate a full markdown report.

Frequently Asked Questions about differential-review

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

FAQPage Schema
How do I review a PR for security vulnerabilities?▼

Run a differential security review on the PR's commit range. The workflow triages changed files by risk level, analyzes diffs with git blame, checks test coverage, calculates blast radius, and produces a markdown report with findings and recommendations.

How to detect security regressions in code changes?▼

Use git log -S and git blame on removed code to find when it was added and why. Code removed in commits mentioning security, fix, or CVE that gets re-added is flagged as a regression requiring immediate escalation.

What is blast radius analysis in code review?▼

Blast radius counts how many callers a modified function has, classified as LOW (1-5), MEDIUM (6-20), HIGH (21-50), or CRITICAL (50+). Combined with change risk level, it determines review priority and analysis depth.

Does this work for large codebases with hundreds of files?▼

Yes, it adapts strategy by codebase size: DEEP for under 20 files, FOCUSED for 20-200 files, and SURGICAL for 200+ files where only critical paths receive full analysis. Coverage limitations are stated honestly in the report.

When should I not use differential security review?▼

Avoid it for greenfield code with no baseline to compare, documentation-only changes, formatting or linting updates, and when the user explicitly requests only a quick summary. Standard code review fits those cases better.

What vulnerability patterns does differential review detect?▼

It detects security regressions, missing validation, reentrancy, access control bypass, integer underflow/overflow, unchecked return values, front-running, timestamp manipulation, double accounting bugs, and denial of service patterns.