bmad-checkpoint-preview

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-checkpoint-preview-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-checkpoint-preview
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-checkpoint-preview
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-checkpoint-preview-asygnuz-s-a-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a code change without context is slow and error-prone. This Skill turns an LLM into a guided review companion that orients you on a change's intent, walks you through its design concerns, surfaces high-risk spots, and suggests how to observe the behavior before you approve or reject it. ## Core Features & Use Cases - Structured Review Trail: Identifies the change from a PR, commit, branch, or spec, computes diff statistics, and builds an ordered review trail of concerns with clickable path:line stops. - Risk and Detail Pass: Scans the diff for risk-sensitive patterns (auth, schema, billing, security, config) and surfaces machine-hardening findings from spec change logs. - Experiential Testing Suggestions: Proposes concrete manual actions and expected outcomes so reviewers can observe the change's behavior directly. - Use Case: After a teammate opens a PR touching authentication middleware, trigger the checkpoint workflow to get an intent summary, a concern-grouped walkthrough, a list of auth and security risk spots, and manual verification steps before approving. ## Quick Start Say "checkpoint" or "walk me through this change" to start a guided human review of the current PR, commit, or branch.

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 pull request with an AI assistant?▼

Trigger the checkpoint workflow with a PR reference, and it resolves the branch via gh pr view, summarizes intent, computes diff stats, and walks you through concerns with clickable path:line stops. It ends with an approve, rework, or discuss decision prompt.

How does the checkpoint review find what change to review?▼

It checks in order: an explicit PR, commit, branch, or spec argument; recent conversation context; sprint status files for stories marked review; and the current git HEAD. If none identify a change, it asks you directly.

What happens if there is no spec or review trail for a commit?▼

The skill falls back to generating a review trail from the diff itself, reading changed files in full to identify two to five design concerns with ordered stops. If git is unavailable, it continues with a non-trail walkthrough path.

Can I customize the checkpoint workflow steps?▼

Yes, a customize.toml file supports prepend and append activation steps, persistent facts loaded from files or globs, and an on_complete hook. Team and user override files merge with the defaults using structural merge rules.

What risk categories does the detail pass detect?▼

It scans the diff for auth, public API, schema, billing, infra, security, and config changes, plus an open-ended other category. Spots are ordered by blast radius, and if nothing risk-sensitive exists it says so rather than inventing findings.