differential-review

Performs security-focused differential review of code changes across PRs, commits, and diffs.

Updated May 17, 2026
One-click install
npx skills add https://github.com/irrit-us/agent_misc --skill differential-review-irrit-us
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: differential-review
Source: https://github.com/irrit-us/agent_misc/tree/main/skills/differential-review
Command: npx skills add https://github.com/irrit-us/agent_misc --skill differential-review-irrit-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing code changes for security regressions is error-prone: reviewers miss removed validation checks, re-introduced vulnerabilities, and high blast-radius changes hidden in large diffs. This Skill provides a structured, evidence-based methodology to catch security regressions before merge. ## Core Features & Use Cases - Risk-Adaptive Analysis: Classifies changes by risk level (HIGH/MEDIUM/LOW) and adapts review depth to codebase size (SMALL/MEDIUM/LARGE) so effort goes where it matters. - Git History & Blast Radius Analysis: Uses git blame and commit history to detect regressions of previous security fixes, and quantifies caller impact to prioritize findings. - Adversarial Modeling & Reporting: Builds concrete attacker models and exploit scenarios for high-risk changes, then generates a comprehensive markdown report with severity ratings and recommendations. - Use Case: A team is merging an 80-file PR that touches an authentication module. Use this Skill to triage the 12 high-risk files, run git blame on removed access-control checks, model an exploit scenario, and produce a report recommending REJECT until the authorization bypass is fixed. ## Quick Start Ask the AI to perform a differential security review of the current PR or commit range and generate a markdown report of all findings.

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?▼

Use a differential review workflow: extract the diff with git or gh CLI, risk-classify each changed file, run git blame on removed security checks, calculate blast radius by counting callers, and model attack scenarios for high-risk changes. This Skill automates that full methodology and outputs a markdown report.

How to detect security regressions in code changes with git?▼

Run git log -S with the removed code pattern and grep commit messages for 'security', 'fix', or 'CVE'. Code previously removed in a security fix that reappears in a new diff is a regression and should be flagged as critical.

What is blast radius analysis in code review?▼

Blast radius analysis counts how many callers a modified function has, using grep across the codebase. Changes with 50+ callers combined with high-risk modifications get top priority for deep analysis, since a flaw propagates widely.

When should I not use differential security review?▼

Skip it for greenfield code with no baseline to compare, documentation-only changes, formatting or linting commits, and when the user explicitly requests only a quick summary. Standard code review is sufficient in those cases.

Does differential review work for large codebases?▼

Yes. For codebases over 200 files it uses a SURGICAL strategy that analyzes only critical paths and high-risk changes, while small codebases under 20 files get deep analysis of all dependencies with full git blame.