differential-review

Performs security-focused differential review of code changes with git history analysis and markdown reports.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill differential-review-ayoub-ouederni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: differential-review
Source: https://github.com/Ayoub-ouederni/SENTINEL/tree/main/.claude/skills/differential-review
Command: npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill differential-review-ayoub-ouederni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss security regressions hidden in diffs, especially when reviewers skip git history or underestimate small changes. This Skill systematically analyzes PRs, commits, and diffs to detect removed validations, access control bypasses, reentrancy risks, and other vulnerabilities before they reach production. ## 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: Uses git blame and log searches to detect security regressions, and quantifies blast radius by counting callers of modified functions. - Adversarial Modeling & Reporting: Builds concrete attacker models and exploit scenarios for HIGH RISK changes, then generates a structured markdown report with severity tables, findings, and recommendations. - Use Case: A smart contract PR removes a require(amount > 0) check. The Skill traces the check's origin via git blame, finds it was added to fix a prior exploit, rates exploitability as EASY, and flags the change as CRITICAL in the final report. ## Quick Start Ask the AI to run a differential security review on the current PR or commit range and generate the 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 review that classifies each changed file by risk level, then applies git blame to removed code, calculates blast radius for modified functions, and builds attack scenarios for HIGH RISK changes. The output is a markdown report with severity-rated findings and recommendations.

How to detect security regressions in code changes?

Use git log -S to search whether removed code originated from commits mentioning security, fix, or CVE. Code added, removed for security reasons, then re-added indicates a regression and should be escalated to adversarial analysis.

What vulnerability patterns does differential review check for?

It checks for removed validations, reentrancy, access control bypass, integer underflow/overflow, unchecked return values, front-running, timestamp manipulation, denial of service, and double accounting bugs. Detection uses git diff greps for removed require statements and changed modifiers.

Does this review approach work for large codebases?

Yes, it adapts strategy by codebase size: deep analysis for under 20 files, focused one-hop dependency analysis for 20-200 files, and surgical critical-path-only review for 200+ files. Risk classification ensures high-risk changes always get full analysis.

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 when the user explicitly requests only a quick summary. Standard code review fits those cases better.