bmad-checkpoint-preview

A human-in-the-loop code review guides a reviewer from purpose and context into concrete details. It uses PR, commit, or branch references to determine what changed, highlighting high-blast-radius areas like auth, public API, schema, security, and infra for focused attention.

A checkpoint review in change management is an LLM-assisted walkthrough that helps you understand and sanity-check a proposed change before approval. It produces an orientation, a walkthrough, and a risk-focused detail pass to reduce the risk of missing real intent or critical side effects.

To assess risk in a git diff before merging, a structured review highlights high-blast-radius areas such as authentication, public APIs, schemas, security, and infrastructure. This risk-aware thinking focuses your attention on critical side effects during the checkpoint evaluation.

Yes, you can review code changes using conversation context if no spec exists. The review process generates a structured review ordering as a fallback, while enriching the change context resolution with available specifications when they are present.

The best way to walk through what a code change does and why is triggering a guided checkpoint workflow. It produces a suggested review trail and provides a structured walkthrough, moving from general purpose and context into concrete, risk-focused details.

Workflow orchestration for change management requires resolving workflow configuration and loading persistent facts. This setup ensures the human reviewer receives accurate orientation and risk-focused details before approving the proposed change.