differential-review
💡 摘要
一个专注于安全的工具,用于审查代码更改以识别漏洞和评估影响。
🎯 适合人群
🤖 AI 吐槽: “看起来很能打,但别让配置把人劝退。”
风险:Medium。建议检查:是否执行 shell/命令行指令;API Key/Token 的获取、存储与泄露风险。以最小权限运行,并在生产环境启用前审计代码与依赖。
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:
- Pre-Analysis - Build baseline context with
audit-context-buildingskill (if available) - Phase 0: Intake - Extract changes, assess size, risk-score files
- Phase 1: Changed Code - Analyze diffs, git blame, check for regressions
- Phase 2: Test Coverage - Identify coverage gaps
- Phase 3: Blast Radius - Calculate impact of changes
- Phase 4: Deep Context - Five Whys root cause analysis
- Phase 5: Adversarial Analysis - Hunt vulnerabilities with attacker model
- 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 analysisissue-writer- Transform findings into formal audit reports
优点
- 全面的安全分析
- 模块化文档,便于导航
- 适应不同代码库规模的深度分析
- 生成可操作的报告
缺点
- 需要熟悉git
- 可能需要额外的上下文构建技能
- 复杂性可能让新用户感到不知所措
- 依赖外部工具以实现完整功能
相关技能
免责声明:本内容来源于 GitHub 开源项目,仅供展示和评分分析使用。
版权归原作者所有 trailofbits.
