differential review

Engineering Community

Skill notes

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

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

Decision Tree

Starting a review?

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview differential-review.preview
# Tips for Best Results

- 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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.