bmad-checkpoint-preview

Structured code review organizes a pull request diff into orientation, walkthrough, risk, and testing phases to evaluate design intent and verify observable behavior. This approach helps reviewers trace key paths and decide where to focus their attention before making a ship or rework decision.

Blast radius assessment identifies high-risk areas in a diff such as authentication, schema modifications, public APIs, and infrastructure. By grouping changes by design intent rather than by file, reviewers can pinpoint critical paths and evaluate the potential impact of the implementation.

Concern-based diff analysis groups code changes by design intent instead of separating them by file. This helps reviewers understand the reasoning behind the implementation and trace the logical flow of the changes throughout the commit.

Yes, this code review workflow applies to individual commits, branches, and specifications. It requires diff context and path:line citations to generate reviewer-ready metadata and trace the review order effectively across different types of version control changes.

Without path:line citations, the review lacks the specific context needed to trace key paths and produce reviewer-ready metadata. Accurate risk assessment and testing guidance depend on having precise diff context to verify observable behavior.