differential-review

You can automate security-focused code review for a pull request by running a differential review that applies phase-based analysis to the diff, estimates blast radius, and generates a markdown audit report.

Blast radius estimation in a differential code review calculates the potential impact scope of code changes by analyzing git history and dependencies to prevent security regressions.

Yes, automated diff review adapts its analysis depth to codebase size, using git history for baseline context to triage and analyze changes across small to large repositories.

To generate a formal markdown report from a git diff, execute a differential review workflow that assesses test coverage, performs change analysis, and outputs structured audit findings.

Yes, automated differential review works with individual git commits, applying the same security-focused triage, blast radius calculation, and test coverage assessment used for PR diffs.

You should use an automated security review instead of manual code checks when standardizing differential analysis across many PRs to reduce time-consuming human error and prevent security regressions.