differential-review

Security-focused code review on a PR analyzes diffs to identify regressions and risks. It adapts review depth based on codebase size and uses git history for context to produce a detailed markdown report with blast-radius calculations.

Blast-radius calculation in differential code review measures the potential impact of code changes across the codebase. It evaluates the scope of regressions and security risks by analyzing diffs and git history to produce risk-based triage evidence.

Test coverage checks during git diff security analysis verify existing tests against modified code. The differential review process evaluates coverage alongside risk-based triage and blast-radius calculations to ensure regressions are caught.

Adaptive code review works for large codebases by scaling review depth according to size classifications like SMALL, MEDIUM, and LARGE. It leverages git history for context to maintain accurate risk-analysis and regression detection.

Git history can be used to find security regressions in commits by providing contextual background for differential review. This approach traces code changes over time to identify risk patterns in auth, crypto, and external calls.

The best way to generate a risk-analysis report for code changes is performing a differential review that integrates audit-context-building and issue-writer workflows. It outputs a comprehensive markdown report with concrete findings and line-number references.