differential-review

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

507|40|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/waybarrios/opencode-power-pack --skill differential-review-waybarrios
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: differential-review
Source: https://github.com/waybarrios/opencode-power-pack/tree/main/skills/differential-review
Command: npx skills add https://github.com/waybarrios/opencode-power-pack --skill differential-review-waybarrios

SYSTEM DOCUMENTATION & REQUIREMENTS

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 untested high-risk changes, especially in large codebases. ## 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) using DEEP, FOCUSED, or SURGICAL strategies. - Git History & Blast Radius: Uses git blame and log searches to detect security regressions, calculates caller counts to quantify blast radius, and checks test coverage gaps. - Adversarial Modeling & Reporting: Builds concrete attacker models and exploit scenarios for HIGH RISK changes, then generates a comprehensive markdown report with severity tables, findings, and recommendations. - Use Case: A team merging an auth system rewrite across 450 files uses this Skill to baseline the original code, deep-analyze only the auth changes, model exploit scenarios, and produce a blocking/conditional merge recommendation report. ## Quick Start Ask the AI to perform a differential security review of the current pull request or commit range 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?▼

Run a differential security review on the PR's commit range. The workflow triages changed files by risk level, analyzes diffs with git blame, checks test coverage, calculates blast radius, and generates a markdown report with severity-rated findings.

How to detect security regressions in code changes?▼

Use git log -S searches to find code previously removed in security or CVE fix commits that has been re-added. The review flags removed require/assert checks, relaxed access modifiers, and re-introduced vulnerable patterns as regressions.

What is blast radius analysis in code review?▼

Blast radius analysis counts how many callers invoke each modified function using grep across the codebase. Functions with 50+ callers combined with HIGH risk changes get top priority for deep analysis and adversarial modeling.

Does differential review work for large codebases?▼

Yes, it adapts strategy to 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. Large reviews take roughly 6-8 hours.

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.