differential-review

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

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Surojit012/CMO --skill differential-review-surojit012
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: differential-review
Source: https://github.com/Surojit012/CMO/tree/main/.agents/skills/differential-review
Command: npx skills add https://github.com/Surojit012/CMO --skill differential-review-surojit012

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss security regressions hidden in diffs, especially when validation checks are removed or previously fixed vulnerabilities are reintroduced. This Skill systematically analyzes PRs, commits, and diffs to detect security regressions, missing test coverage, and high blast radius changes before they reach production. ## Core Features & Use Cases - Risk-Adaptive Analysis: Classifies codebases as SMALL, MEDIUM, or LARGE and scales review depth accordingly, prioritizing HIGH RISK changes like auth, crypto, and value transfer logic. - Git History Forensics: Uses git blame and commit history to detect removed security checks, re-added vulnerable code, and regressions of previous CVE fixes. - Adversarial Modeling: Builds concrete attacker models and step-by-step exploit scenarios with exploitability ratings for HIGH RISK changes. - Use Case: A team submits a PR modifying a withdraw function in a smart contract. The Skill detects a removed require check, traces it back to a prior security fix commit, calculates that 23 callers are affected, and generates a markdown report with a CRITICAL finding and proof-of-concept exploit. ## Quick Start Ask the AI to perform a differential security review of the changes between two commits or a pull request 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 pull request for security vulnerabilities?

Provide the PR number or commit range and the Skill extracts the diff, risk-scores each changed file, runs git blame on removed code, and generates a markdown report with findings. HIGH RISK changes like auth or validation removal get adversarial exploit scenario analysis.

How to detect security regressions in code changes?

The Skill uses git log -S to search history for removed code patterns and flags commits mentioning security, fix, or CVE. If previously removed vulnerable code is re-added, it is flagged as a regression with the original commit reference.

What is blast radius analysis in code review?

Blast radius counts how many callers invoke each modified function using grep across the codebase. Functions with 50+ callers are CRITICAL priority, and high blast radius combined with HIGH risk changes triggers the deepest analysis.

Does this work for large codebases with hundreds of files?

Yes, the Skill adapts strategy by codebase size: DEEP analysis 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 commits, and cases where the user explicitly wants only a quick summary. Standard code review fits those scenarios better.

What output does the differential review produce?

It always generates a persistent markdown report file containing an executive summary, severity-rated findings with line numbers and commit references, test coverage analysis, blast radius tables, and recommendations. The report can feed into the issue-writer skill for stakeholder-ready audit documents.