differential-review

Automating security-focused code reviews involves analyzing git diffs and commits to identify risks. This skill processes baseline context, calculates blast radius, and generates adversarial reports with concrete exploit scenarios for triaging code changes.

Blast radius calculation in diff analysis measures the potential impact of code changes across a codebase. It evaluates test coverage and baseline context to stratify risk levels, helping prioritize security findings during pull request triage and auditing.

Generating security audit reports from git history requires comparing base and head commits to drive a phase-based workflow. The process produces comprehensive markdown audit reports, integrating risk classification, deep context, and executive reporting for stakeholders.

Yes, this risk assessment approach handles complex diffs across varying codebases using a phase-driven methodology. It spans from pre-analysis and Phase 0 triage through Phase 6 reporting, adapting context-aware risk scoring to different project structures.

Classifying security vulnerabilities in commit diffs uses context-aware risk scoring to flag changes as HIGH, MEDIUM, or LOW risk. The methodology derives blast radius and generates concrete exploit scenarios to categorize findings during adversarial reporting.

The best way to triage security regressions in code changes is integrating git history with baseline context and test coverage analyses. This approach drives adversarial reporting, calculating blast radius to detect security gaps and regressions across commits.