differential-review

Automated security review for a PR diff analyzes baseline and head commits to surface vulnerabilities and regressions. It adapts analysis depth based on codebase risk, producing a markdown audit report with blast radius calculations and remediation guidance.

Blast radius calculation in code review measures the potential impact of code changes across the codebase by comparing baseline and head commits. It identifies trust boundary violations and surfaces concrete vulnerabilities to ensure defense-in-depth in the audit report.

To generate an audit report for authentication code changes, run a differential review on the PR diff. The skill provides concrete findings, blast radius impact, and remediation guidance by applying phase-driven triage and code analysis.

Baseline context is used to detect security regressions in a PR by building and preserving a baseline to identify invariants and trust boundary violations. This phase-driven analysis compares baseline and head commits to surface concrete vulnerabilities.

Automated PR audit adapts to large codebases by scaling analysis depth based on codebase size and risk. It applies phase-driven review including triage, code analysis, and deep context to produce a comprehensive markdown report for stakeholders.

Automated security review for code diffs is not suited for non-security-focused analysis or when baseline and head commits are unavailable. It requires a git-based diff to compare changes and calculate blast radius for trust boundary violations.