Differential Security Review
Security-focused code review for PRs, commits, and diffs.
When to Use
- You need a security-focused review of a PR, commit range, or diff rather than a general code review.
- The changes touch auth, crypto, external calls, value transfer, permissions, or other high-risk logic.
- You need findings backed by code evidence, attack scenarios, and an explicit report artifact.
Core Principles
- Risk-First: Focus on auth, crypto, value transfer, external calls
- Evidence-Based: Every finding backed by git history, line numbers, attack scenarios
- Adaptive: Scale to codebase size (SMALL/MEDIUM/LARGE)
- Honest: Explicitly state coverage limits and confidence level
- Output-Driven: Always generate comprehensive markdown report file
Rationalizations (Do Not Skip)
| Rationalization |
Why It's Wrong |
Required Action |
| "Small PR, quick review" |
Heartbleed was 2 lines |
Classify by RISK, not size |
| "I know this codebase" |
Familiarity breeds blind spots |
Build explicit baseline context |
| "Git history takes too long" |
History reveals regressions |
Never skip Phase 1 |
| "Blast radius is obvious" |
You'll miss transitive callers |
Calculate quantitatively |
| "No tests = not my problem" |
Missing tests = elevated risk rating |
Flag in report, elevate severity |
| "Just a refactor, no security impact" |
Refactors break invariants |
Analyze as HIGH until proven LOW |
| "I'll explain verbally" |
No artifact = findings lost |
Always write report |
Quick Reference
Codebase Size Strategy
| Codebase Size |
Strategy |
Approach |
| SMALL (<20 files) |
DEEP |
Read all deps, full git blame |
| MEDIUM (20-200) |
FOCUSED |
1-hop deps, priority files |
| LARGE (200+) |
SURGICAL |
Critical paths only |
Risk Level Triggers
| Risk Level |
Triggers |
| HIGH |
Auth, crypto, external calls, value transfer, validation removal |
| MEDIUM |
Business logic, state changes, new public APIs |
| LOW |
Comments, tests, UI, logging |
Workflow Overview
Pre-Analysis → Phase 0: Triage → Phase 1: Code Analysis → Phase 2: Test Coverage
↓ ↓ ↓ ↓
Phase 3: Blast Radius → Phase 4: Deep Context → Phase 5: Adversarial → Phase 6: Report
Decision Tree
Starting a review?
├─ Need detailed phase-by-phase methodology?
│ └─ Read: methodology.md
│ (Pre-Analysis + Phases 0-4: triage, code analysis, test coverage, blast radius)
│
├─ Analyzing HIGH RISK change?
│ └─ Read: adversarial.md
│ (Phase 5: Attacker modeling, exploit scenarios, exploitability rating)
│
├─ Writing the final report?
│ └─ Read: reporting.md
│ (Phase 6: Report structure, templates, formatting guidelines)
│
├─ Looking for specific vulnerability patterns?
│ └─ Read: patterns.md
│ (Regressions, reentrancy, access control, overflow, etc.)
│
└─ Quick triage only?
└─ Use Quick Reference above, skip detailed docs
Quality Checklist
Before delivering:
Integration
audit-context-building skill:
- Pre-Analysis: Build baseline context
- Phase 4: Deep context on HIGH RISK changes
issue-writer skill:
- Transform findings into formal audit reports
- Command:
issue-writer --input DIFFERENTIAL_REVIEW_REPORT.md --format audit-report
Example Usage
Quick Triage (Small PR)
Input: 5 file PR, 2 HIGH RISK files
Strategy: Use Quick Reference
1. Classify risk level per file (2 HIGH, 3 LOW)
2. Focus on 2 HIGH files only
3. Git blame removed code
4. Generate minimal report
Time: ~30 minutes
Standard Review (Medium Codebase)
Input: 80 files, 12 HIGH RISK changes
Strategy: FOCUSED (see methodology.md)
1. Full workflow on HIGH RISK files
2. Surface scan on MEDIUM
3. Skip LOW risk files
4. Complete report with all sections
Time: ~3-4 hours
Deep Audit (Large, Critical Change)
Input: 450 files, auth system rewrite
Strategy: SURGICAL + audit-context-building
1. Baseline context with audit-context-building
2. Deep analysis on auth changes only
3. Blast radius analysis
4. Adversarial modeling
5. Comprehensive report
Time: ~6-8 hours
When NOT to Use This Skill
- Greenfield code (no baseline to compare)
- Documentation-only changes (no security impact)
- Formatting/linting (cosmetic changes)
- User explicitly requests quick summary only (they accept risk)
For these cases, use standard code review instead.
Red Flags (Stop and Investigate)
Immediate escalation triggers:
- Removed code from "security", "CVE", or "fix" commits
- Access control modifiers removed (onlyOwner, internal → external)
- Validation removed without replacement
- External calls added without checks
- High blast radius (50+ callers) + HIGH risk change
These patterns require adversarial analysis even in quick triage.
Tips for Best Results
Do:
- Start with git blame for removed code
- Calculate blast radius early to prioritize
- Generate concrete attack scenarios
- Reference specific line numbers and commits
- Be honest about coverage limitations
- Always generate the output file
Don't:
- Skip git history analysis
- Make generic findings without evidence
- Claim full analysis when time-limited
- Forget to check test coverage
- Miss high blast radius changes
- Output report only to chat (file required)
Supporting Documentation
- methodology.md - Detailed phase-by-phase workflow (Phases 0-4)
- adversarial.md - Attacker modeling and exploit scenarios (Phase 5)
- reporting.md - Report structure and formatting (Phase 6)
- patterns.md - Common vulnerability patterns reference
For first-time users: Start with methodology.md to understand the complete workflow.
For experienced users: Use this page's Quick Reference and Decision Tree to navigate directly to needed content.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: differential-review3description: "Security-focused code review for PRs, commits, and diffs."4risk: critical5source: community6date_added: "2026-03-06"7metadata:8 source: https://skillmd.com/skills/iradoweck/differential-review9---1011# Differential Security Review1213Security-focused code review for PRs, commits, and diffs.1415## When to Use16- You need a security-focused review of a PR, commit range, or diff rather than a general code review.17- The changes touch auth, crypto, external calls, value transfer, permissions, or other high-risk logic.18- You need findings backed by code evidence, attack scenarios, and an explicit report artifact.1920## Core Principles21221. **Risk-First**: Focus on auth, crypto, value transfer, external calls232. **Evidence-Based**: Every finding backed by git history, line numbers, attack scenarios243. **Adaptive**: Scale to codebase size (SMALL/MEDIUM/LARGE)254. **Honest**: Explicitly state coverage limits and confidence level265. **Output-Driven**: Always generate comprehensive markdown report file2728---2930## Rationalizations (Do Not Skip)3132| Rationalization | Why It's Wrong | Required Action |33|-----------------|----------------|-----------------|34| "Small PR, quick review" | Heartbleed was 2 lines | Classify by RISK, not size |35| "I know this codebase" | Familiarity breeds blind spots | Build explicit baseline context |36| "Git history takes too long" | History reveals regressions | Never skip Phase 1 |37| "Blast radius is obvious" | You'll miss transitive callers | Calculate quantitatively |38| "No tests = not my problem" | Missing tests = elevated risk rating | Flag in report, elevate severity |39| "Just a refactor, no security impact" | Refactors break invariants | Analyze as HIGH until proven LOW |40| "I'll explain verbally" | No artifact = findings lost | Always write report |4142---4344## Quick Reference4546### Codebase Size Strategy4748| Codebase Size | Strategy | Approach |49|---------------|----------|----------|50| SMALL (<20 files) | DEEP | Read all deps, full git blame |51| MEDIUM (20-200) | FOCUSED | 1-hop deps, priority files |52| LARGE (200+) | SURGICAL | Critical paths only |5354### Risk Level Triggers5556| Risk Level | Triggers |57|------------|----------|58| HIGH | Auth, crypto, external calls, value transfer, validation removal |59| MEDIUM | Business logic, state changes, new public APIs |60| LOW | Comments, tests, UI, logging |6162---6364## Workflow Overview6566```67Pre-Analysis → Phase 0: Triage → Phase 1: Code Analysis → Phase 2: Test Coverage68 ↓ ↓ ↓ ↓69Phase 3: Blast Radius → Phase 4: Deep Context → Phase 5: Adversarial → Phase 6: Report70```7172---7374## Decision Tree7576**Starting a review?**7778```79├─ Need detailed phase-by-phase methodology?80│ └─ Read: methodology.md81│ (Pre-Analysis + Phases 0-4: triage, code analysis, test coverage, blast radius)82│83├─ Analyzing HIGH RISK change?84│ └─ Read: adversarial.md85│ (Phase 5: Attacker modeling, exploit scenarios, exploitability rating)86│87├─ Writing the final report?88│ └─ Read: reporting.md89│ (Phase 6: Report structure, templates, formatting guidelines)90│91├─ Looking for specific vulnerability patterns?92│ └─ Read: patterns.md93│ (Regressions, reentrancy, access control, overflow, etc.)94│95└─ Quick triage only?96 └─ Use Quick Reference above, skip detailed docs97```9899---100101## Quality Checklist102103Before delivering:104105- [ ] All changed files analyzed106- [ ] Git blame on removed security code107- [ ] Blast radius calculated for HIGH risk108- [ ] Attack scenarios are concrete (not generic)109- [ ] Findings reference specific line numbers + commits110- [ ] Report file generated111- [ ] User notified with summary112113---114115## Integration116117**audit-context-building skill:**118- Pre-Analysis: Build baseline context119- Phase 4: Deep context on HIGH RISK changes120121**issue-writer skill:**122- Transform findings into formal audit reports123- Command: `issue-writer --input DIFFERENTIAL_REVIEW_REPORT.md --format audit-report`124125---126127## Example Usage128129### Quick Triage (Small PR)130```131Input: 5 file PR, 2 HIGH RISK files132Strategy: Use Quick Reference1331. Classify risk level per file (2 HIGH, 3 LOW)1342. Focus on 2 HIGH files only1353. Git blame removed code1364. Generate minimal report137Time: ~30 minutes138```139140### Standard Review (Medium Codebase)141```142Input: 80 files, 12 HIGH RISK changes143Strategy: FOCUSED (see methodology.md)1441. Full workflow on HIGH RISK files1452. Surface scan on MEDIUM1463. Skip LOW risk files1474. Complete report with all sections148Time: ~3-4 hours149```150151### Deep Audit (Large, Critical Change)152```153Input: 450 files, auth system rewrite154Strategy: SURGICAL + audit-context-building1551. Baseline context with audit-context-building1562. Deep analysis on auth changes only1573. Blast radius analysis1584. Adversarial modeling1595. Comprehensive report160Time: ~6-8 hours161```162163---164165## When NOT to Use This Skill166167- **Greenfield code** (no baseline to compare)168- **Documentation-only changes** (no security impact)169- **Formatting/linting** (cosmetic changes)170- **User explicitly requests quick summary only** (they accept risk)171172For these cases, use standard code review instead.173174---175176## Red Flags (Stop and Investigate)177178**Immediate escalation triggers:**179- Removed code from "security", "CVE", or "fix" commits180- Access control modifiers removed (onlyOwner, internal → external)181- Validation removed without replacement182- External calls added without checks183- High blast radius (50+ callers) + HIGH risk change184185These patterns require adversarial analysis even in quick triage.186187---188189## Tips for Best Results190191**Do:**192- Start with git blame for removed code193- Calculate blast radius early to prioritize194- Generate concrete attack scenarios195- Reference specific line numbers and commits196- Be honest about coverage limitations197- Always generate the output file198199**Don't:**200- Skip git history analysis201- Make generic findings without evidence202- Claim full analysis when time-limited203- Forget to check test coverage204- Miss high blast radius changes205- Output report only to chat (file required)206207---208209## Supporting Documentation210211- **methodology.md** - Detailed phase-by-phase workflow (Phases 0-4)212- **adversarial.md** - Attacker modeling and exploit scenarios (Phase 5)213- **reporting.md** - Report structure and formatting (Phase 6)214- **patterns.md** - Common vulnerability patterns reference215216---217218**For first-time users:** Start with methodology.md to understand the complete workflow.219220**For experienced users:** Use this page's Quick Reference and Decision Tree to navigate directly to needed content.221222## Limitations223- Use this skill only when the task clearly matches the scope described above.224- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.225- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.