A09 — PR / Git Diff Review

Review a pull request diff by analyzing git refs to identify build breaks or contract violations in Java Spring Boot code, anchoring findings to exact file paths and line numbers for traceable risk assessment.

Blast radius classification in code review categorizes diff changes into CRITICAL, HIGH, MEDIUM, and LOW risk levels, evaluating the potential impact scope of modifications to guide targeted remediation and rollback planning.

Identify test gaps from a git diff by analyzing the changes between two refs to detect modified code paths lacking corresponding test coverage, generating structured reports to guide developers on what to fix before merge.

Yes, you can assess pull request risk by analyzing the diff from the last 10 commits instead of specific git refs, producing the same structured risk assessment with findings anchored to exact files and lines.

This code review approach is specifically designed for Java and Spring Boot projects. Its diff analysis, risk scoring, and blast radius classification are tailored to the structures and contracts found in Java Spring applications.

Plan a rollback for high-risk Spring Boot changes by reviewing the structured risk assessment generated from the diff, which classifies risk severity and proposes targeted remediation and rollback steps for CRITICAL and HIGH changes.