bmad-checkpoint-preview

Guide structured human review of repository diffs with risk and testing cues.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-checkpoint-preview-mol4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-checkpoint-preview
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-checkpoint-preview
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-checkpoint-preview-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers make sense of code changes quickly, separating intent, design concerns, risks, and ways to observe behavior before deciding whether to approve or rework.

Core Features & Use Cases

  • Guided orientation: Establishes what changed, why it changed, and how large the review surface is.
  • Concern-based walkthrough: Groups files and stops by design intent so reviewers can follow the logic instead of scanning mechanically.
  • Risk and testing cues: Highlights high-blast-radius spots and suggests practical ways to see the change working.
  • Use case: Use it when you are reviewing a pull request, commit, branch, or spec-driven change and need a structured, high-signal review.

Quick Start

Ask me to review the change you want checked, and I will guide you through orientation, walkthrough, detail pass, and testing.

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 high blast-radius changes?

Reviewing a pull request with high blast-radius changes requires grouping files by design intent and spotting critical risk areas. This Skill guides you through structured orientation, concern-based walkthroughs, and observable testing suggestions derived from repository diffs to ensure confident approvals.

What is the best way to structure a code review for repository commits?

A structured code review separates intent, design concerns, risks, and verification steps. This Skill provides context-aware walkthroughs that group files by design logic, perform blast-radius analysis, and highlight risk spots so reviewers can follow the change instead of scanning mechanically.

Can I use this for reviewing spec-driven design artifacts and branches?

Yes, you can review spec-driven design artifacts and branches. This Skill applies to any repository change or supporting spec, establishing what changed and why, generating a review trail, and providing verification guidance for design artifacts and branch diffs.

How do I generate a review trail for a repository diff?

Generating a review trail for a repository diff requires establishing the change surface and grouping concerns by design intent. This Skill produces context-aware walkthroughs and blast-radius analysis, creating a structured trail that separates intent, risks, and testing suggestions.

Does this code review skill suggest testing strategies for pull requests?

Yes, this code review skill suggests observable testing strategies for pull requests. It highlights high blast-radius spots in repository diffs and recommends practical, observable ways to see the change working, guiding you through testing during the detail pass phase.