bmad-checkpoint-preview

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

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-checkpoint-preview-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-checkpoint-preview
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-checkpoint-preview
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-checkpoint-preview-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a code change without structure leads to missed risks and shallow approvals. This Skill walks a human reviewer through a change step by step — from understanding intent, to a concern-based walkthrough, to risk surfacing, to hands-on verification — so the review decision is informed. ## Core Features & Use Cases - Change Orientation: Identifies the change from PRs, commits, branches, specs, or sprint status, then summarizes intent and surface-area stats (files, modules, boundary crossings). - Guided Walkthrough: Organizes the diff by design concern with clickable path:line stops, generating a review trail when the author didn't provide one. - Risk & Testing Passes: Surfaces high-blast-radius spots (auth, schema, billing, security) and suggests concrete ways to observe the changed behavior manually. - Use Case: After a teammate opens a PR, say "walk me through this change" and get a structured review trail ending in an approve, rework, or discuss decision. ## Quick Start Ask the assistant to walk you through the current branch or a specific PR as a checkpoint review.

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 review with a PR reference, branch, or commit. The skill resolves the change, summarizes its intent and diff stats, then walks you through concerns, risk spots, and testing suggestions before you decide to approve or request rework.

How does the review walkthrough organize a large diff?

It groups changes by design concern rather than by file, ordering stops so each builds on the previous one. Each stop is a clickable path:line reference with a short framing phrase, targeting two to five concerns per change.

What happens if the change has no spec or review trail?

The skill generates a review trail from the diff itself by reading changed files and identifying two to five concerns with key path:line stops. If git is unavailable and no trail can be built, it falls back to a non-trail walkthrough mode.

Can I dig deeper into a specific area during the review?

Yes. During the detail pass you can say "dig into [area]" and the skill switches to correctness mode, reading the relevant code in full context to check edge cases, error handling, race conditions, and boundary conditions.

Does the checkpoint review replace automated tests or CI?

No. It assumes CI and test suites already exist and focuses on human judgment: design evaluation, risk awareness, and manual observation of behavior that automated checks cannot provide.