differential-review

Performs security-focused differential review of pull requests, commits, and diffs with markdown reports.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/NicolaeRotaru/ad-mycity --skill differential-review-nicolaerotaru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: differential-review
Source: https://github.com/NicolaeRotaru/ad-mycity/tree/main/.cursor/skills/differential-review
Command: npx skills add https://github.com/NicolaeRotaru/ad-mycity --skill differential-review-nicolaerotaru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code changes often introduce security regressions that slip through casual review, especially when removed validation, altered access controls, or new external calls go unnoticed. This Skill provides a structured, evidence-based methodology for reviewing diffs so that high-risk changes are caught 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 investigate removed security code and quantitatively calculates how many callers a change affects. - Adversarial Modeling: Builds concrete attacker models and exploit scenarios for high-risk changes, with test coverage checks and a mandatory markdown report. - Use Case: Before merging a PR that modifies authentication logic, run a differential review to detect removed validation, calculate the blast radius across callers, and produce a report with line-number-referenced findings. ## Quick Start Ask the AI to perform a differential security review of the current pull request or a specific commit range and generate the review report.

Frequently Asked Questions about differential-review

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

FAQPage Schema
How do I do a security-focused code review of a pull request?▼

Classify each changed file by risk level, then apply git blame to removed security code, calculate blast radius for high-risk changes, and model concrete attack scenarios. Finish by generating a markdown report with findings referenced to specific lines and commits.

What is differential code review and when should I use it?▼

Differential review analyzes code changes against an existing baseline rather than reviewing code in isolation. Use it for PRs, commits, and diffs touching auth, crypto, validation, or external calls, but not for greenfield code or documentation-only changes.

How do I calculate blast radius for a code change?▼

Blast radius is calculated quantitatively by tracing direct and transitive callers of the changed code. A change with 50 or more callers combined with high-risk modifications triggers mandatory adversarial analysis.

Does this review approach work for large codebases?▼

Yes, the methodology adapts to codebase size: SMALL codebases get deep full-dependency analysis, MEDIUM get focused one-hop dependency review, and LARGE codebases get surgical analysis of critical paths only.

When should I not use differential security review?▼

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