differential-review

To automate a security-focused code review for pull requests, provide the changed code to trigger a six-phase differential review that identifies security regressions. This process calculates blast radius and generates a comprehensive markdown audit report.

A differential review analyzes code changes across commits or PRs to surface security regressions before they ship. It adapts analysis depth based on codebase size and leverages git history context to evaluate blast radius and test coverage.

Yes, you can use git history context to assess the blast radius of code changes during the differential review. The review calculates evidence-backed risk scores and performs adversarial analysis for HIGH-risk changes based on this historical context.

To generate a markdown audit report for security regressions, input the base to head code changes into the automated review workflow. The system evaluates test coverage and risk scoring, outputting a structured markdown report detailing the findings.

Yes, automated differential review works on large codebases by adapting the analysis depth based on the overall codebase size and context. It applies a phase-based workflow from pre-analysis through the final report to ensure comprehensive coverage.