Co-Pilot
Updated a month ago

differential-review

Ttrailofbits
1.8k
trailofbits/skills/plugins/differential-review
86
Agent Score

💡 Summary

A security-focused tool for reviewing code changes to identify vulnerabilities and assess impact.

🎯 Target Audience

Security engineersSoftware developersDevOps teamsQuality assurance testersProject managers

🤖 AI Roast:Powerful, but the setup might scare off the impatient.

Security AnalysisMedium Risk

Risk: Medium. Review: shell/CLI command execution; API keys/tokens handling and storage. Run with least privilege and audit before enabling in production.

Differential Review

Security-focused differential review of code changes with git history analysis and blast radius estimation.

Author: Omar Inuwa

When to Use

Use this skill when you need to:

  • Review PRs, commits, or diffs for security vulnerabilities
  • Detect security regressions (re-introduced vulnerabilities)
  • Analyze the blast radius of code changes
  • Check test coverage gaps for modified code

What It Does

This skill performs comprehensive security review of code changes:

  • Risk-First Analysis - Prioritizes auth, crypto, value transfer, external calls
  • Git History Analysis - Uses blame to understand why code existed and detect regressions
  • Blast Radius Calculation - Quantifies impact by counting callers
  • Test Coverage Gaps - Identifies untested changes
  • Adaptive Depth - Scales analysis based on codebase size (small/medium/large)

Installation

/plugin install trailofbits/skills/plugins/differential-review

Documentation Structure

This skill uses a modular documentation architecture for token efficiency and progressive disclosure:

Core Entry Point

  • SKILL.md - Main entry point (217 lines)
    • Quick reference tables for triage
    • Decision tree routing to detailed docs
    • Quality checklist and red flags
    • Integration with other skills

Supporting Documentation

  • methodology.md - Detailed phase-by-phase workflow (~200 lines)

    • Pre-Analysis: Baseline context building
    • Phase 0: Intake & Triage
    • Phase 1: Changed Code Analysis
    • Phase 2: Test Coverage Analysis
    • Phase 3: Blast Radius Analysis
    • Phase 4: Deep Context Analysis
  • adversarial.md - Attacker modeling and exploit scenarios (~150 lines)

    • Phase 5: Adversarial Vulnerability Analysis
    • Attacker model definition (WHO/ACCESS/INTERFACE)
    • Exploitability rating framework
    • Complete exploit scenario templates
  • reporting.md - Report structure and formatting (~120 lines)

    • Phase 6: Report Generation
    • 9-section report template
    • Formatting guidelines and conventions
    • File naming and notification templates
  • patterns.md - Common vulnerability patterns (~80 lines)

    • Security regressions detection
    • Reentrancy, access control, overflow patterns
    • Quick detection bash commands

Benefits of This Structure

  • Token Efficient - Load only the documentation you need
  • Progressive Disclosure - Quick reference for triage, detailed docs for deep analysis
  • Maintainable - Each concern separated into its own file
  • Navigable - Decision tree routes you to the right document

Workflow

The complete workflow spans Pre-Analysis + Phases 0-6:

  1. Pre-Analysis - Build baseline context with audit-context-building skill (if available)
  2. Phase 0: Intake - Extract changes, assess size, risk-score files
  3. Phase 1: Changed Code - Analyze diffs, git blame, check for regressions
  4. Phase 2: Test Coverage - Identify coverage gaps
  5. Phase 3: Blast Radius - Calculate impact of changes
  6. Phase 4: Deep Context - Five Whys root cause analysis
  7. Phase 5: Adversarial Analysis - Hunt vulnerabilities with attacker model
  8. Phase 6: Report - Generate comprehensive markdown report

Navigation: Use the decision tree in SKILL.md to jump directly to the phase you need.

Output

Generates a markdown report with:

  • Executive summary with severity distribution
  • Critical findings with attack scenarios and PoCs
  • Test coverage analysis
  • Blast radius analysis
  • Historical context and regression risks
  • Actionable recommendations

Example Usage

Review the security implications of this PR:
git diff main..feature/auth-changes

Related Skills

  • context-building - Used for baseline context analysis
  • issue-writer - Transform findings into formal audit reports
5-Dim Analysis
Clarity9/10
Novelty8/10
Utility9/10
Completeness9/10
Maintainability8/10
Pros & Cons

Pros

  • Comprehensive security analysis
  • Modular documentation for easy navigation
  • Adaptive depth for varying codebase sizes
  • Generates actionable reports

Cons

  • Requires familiarity with git
  • May need additional context-building skills
  • Complexity may overwhelm new users
  • Dependency on external tools for full functionality

Related Skills

prowler

A
toolCode Lib
86/ 100

“It's a Swiss Army knife for cloud security, but you'll need a PhD in YAML to configure all its moving parts.”

kubernetes-specialist

A
toolCo-Pilot
86/ 100

“Powerful, but the setup might scare off the impatient.”

cloud-collector

A
toolCo-Pilot
82/ 100

“Powerful, but the setup might scare off the impatient.”

Disclaimer: This content is sourced from GitHub open source projects for display and rating purposes only.

Copyright belongs to the original author trailofbits.