bmad-checkpoint-preview

Name: bmad-checkpoint-preview
Availability: InStock
Author: GenEd

Guide human-assisted review of code diffs with risk scans and verification prompts.

Updated Mar 30, 2026

Search Tags:#testing #diff analysis #code review #pull request #risk assessment #walkthrough #review trail

Ready to run

npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-checkpoint-preview-geneducation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-checkpoint-preview
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-checkpoint-preview
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-checkpoint-preview-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams review code changes with structure, turning a raw diff into a clear guided walkthrough, risk scan, and testing plan so reviewers can focus on the decisions that matter.

Core Features & Use Cases

Review Orientation: Identifies the change, summarizes intent, and estimates surface area so reviewers know what kind of change they are looking at.
Guided Walkthroughs: Groups related stops by concern to explain what the change does and why it was likely made.
Risk Scanning: Highlights high-blast-radius areas such as auth, public APIs, schema changes, infra, security, and config.
Manual Verification: Suggests observable behaviors a human can inspect to confirm the change works in practice.
Use Case: A reviewer can use this Skill to understand a pull request faster, inspect the riskiest code paths first, and decide whether the change is ready to ship.

Quick Start

Ask the skill to review the current change and produce a walkthrough, risk analysis, and testing observations.

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 diff with a structured walkthrough?▼

To review a pull request diff, you provide the baseline diff and repository context to generate a guided walkthrough. This produces an ordered review trail that groups related code changes by concern so reviewers understand the change intent.

What is the best way to identify high-risk areas in a code diff?▼

Identifying high-risk areas in a code diff involves running a risk scan on auth, public APIs, schema changes, and config. The scan highlights these high-blast-radius spots within the changes so reviewers can inspect the riskiest code paths first.

Can I use spec artifacts to guide a code review of commits?▼

Yes, you can use spec artifacts to guide a code review of commits. Providing optional spec artifacts alongside the baseline diff and repository context produces an ordered review trail that aligns the implementation with the original specifications.

How does manual verification work for testing code changes?▼

Manual verification for testing code changes works by suggesting observable behaviors a human can inspect. The skill generates manual verification prompts as part of the testing plan so reviewers can confirm the change works in practice.

Do I need repository context to perform a risk assessment on a branch diff?▼

Yes, you need repository context to perform a risk assessment on a branch diff. The risk assessment requires a baseline diff and repository context to accurately highlight high-blast-radius areas and group concerns within the code changes.

What is a guided review workflow for code changes?▼

A guided review workflow for code changes turns a raw diff into a structured walkthrough, risk scan, and testing plan. It helps reviewers focus on the decisions that matter by estimating the surface area and summarizing the change intent.