bmad-checkpoint-preview

To review a pull request diff, you provide the baseline diff and repository context to generate a guided walkthrough. This produces an ordered review trail that groups related code changes by concern so reviewers understand the change intent.

Identifying high-risk areas in a code diff involves running a risk scan on auth, public APIs, schema changes, and config. The scan highlights these high-blast-radius spots within the changes so reviewers can inspect the riskiest code paths first.

Yes, you can use spec artifacts to guide a code review of commits. Providing optional spec artifacts alongside the baseline diff and repository context produces an ordered review trail that aligns the implementation with the original specifications.

Manual verification for testing code changes works by suggesting observable behaviors a human can inspect. The skill generates manual verification prompts as part of the testing plan so reviewers can confirm the change works in practice.

Yes, you need repository context to perform a risk assessment on a branch diff. The risk assessment requires a baseline diff and repository context to accurately highlight high-blast-radius areas and group concerns within the code changes.

A guided review workflow for code changes turns a raw diff into a structured walkthrough, risk scan, and testing plan. It helps reviewers focus on the decisions that matter by estimating the surface area and summarizing the change intent.