bmad-checkpoint-preview

Guides human reviewers through code changes via structured walkthrough, risk, and testing steps.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-checkpoint-preview-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-checkpoint-preview
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-checkpoint-preview
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-checkpoint-preview-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a code change without structure leads to missed risks and shallow approvals. This Skill turns an LLM into a guided review companion that walks a human through a change's intent, design concerns, high-risk spots, and observable behavior before a ship-or-rework decision. ## Core Features & Use Cases - Orientation & Intent Summary: Identifies the change from PRs, commits, branches, or specs, then summarizes intent and surface-area stats (files changed, boundary crossings, new public interfaces). - Concern-Based Walkthrough: Organizes the diff by design intent rather than by file, with clickable path:line stops ordered for comprehension. - Risk & Testing Passes: Surfaces high-blast-radius spots (auth, schema, billing, security) and suggests manual observations of user-visible behavior. - Use Case: A developer finishes a feature branch and says "walk me through this change" — the Skill generates a review trail, highlights the riskiest lines, suggests how to see it working, and helps reach an approve/rework decision. ## Quick Start Ask the assistant to checkpoint the current branch and walk you through the change step by step.

Frequently Asked Questions about bmad-checkpoint-preview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a code change with an LLM assistant?▼

Trigger the checkpoint workflow by saying "checkpoint" or "walk me through this change" with a PR, commit, or branch reference. The assistant identifies the change, summarizes intent, and guides you through walkthrough, risk, and testing steps.

How does the checkpoint review identify what changed?▼

It checks explicit arguments first, then recent conversation context, sprint status files, and finally the current git branch and HEAD. It uses git diff against a spec baseline, merge-base, or HEAD~1 to compute change statistics.

Can it review a commit without a spec document?▼

Yes. In bare-commit mode it derives intent from the commit message and generates a review trail directly from the diff. If the message is terse, it drafts an inferred intent and flags it for your correction.

What risk categories does the detail pass detect?▼

It scans the diff for auth, public API, schema, billing, infra, security, and config changes, plus a catch-all category for concerns like concurrency or backwards compatibility. Spots are ordered by blast radius, not severity scores.

What happens if git is unavailable during review?▼

Trail generation fails gracefully and the workflow falls back to a non-trail path in the walkthrough step. Surface-area stats are skipped with an explicit note rather than guessed.