differential-review

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

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill differential-review-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: differential-review
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/differential-review
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill differential-review-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing pull requests and commits for security regressions is error-prone: reviewers miss removed validation checks, re-introduced vulnerabilities, and high-impact changes buried in large diffs. This Skill provides a structured, evidence-based workflow that catches 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), focusing effort where it matters. - Git History Forensics: Uses git blame and log searches to detect removed security checks, re-added vulnerable code, and regressions of previous CVE fixes. - Blast Radius & Adversarial Modeling: Quantifies how many callers each changed function affects and builds concrete attacker models with step-by-step exploit scenarios. - Use Case: A team reviews a PR that modifies a smart contract's withdraw function. The Skill detects a removed require(amount > 0) check, traces it back to a prior security fix commit, calculates 23 affected callers, 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 current pull request or commit range and generate a 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?

Run a differential review that classifies each changed file by risk level, uses git blame on removed code, and builds attack scenarios for HIGH risk changes. The workflow ends with a markdown report containing findings, severity ratings, and recommendations.

How to detect security regressions in code changes with git?

Use git log -S to search history for removed or re-added code patterns, and git blame to find when security checks were originally added. Code removed in commits mentioning 'security', 'fix', or 'CVE' that reappears is a regression red flag.

What is blast radius analysis in code review?

Blast radius analysis counts how many callers a modified function has, classifying impact as LOW (1-5), MEDIUM (6-20), HIGH (21-50), or CRITICAL (50+). High blast radius combined with high-risk changes gets priority for deep analysis.

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 fits those cases better.

Does differential review work for large codebases?

Yes, it 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.