skills.rest
Rinzler78
Rinzler78COMMUNITY
Explore all skills by this author →
GitHub

bmad-checkpoint-preview

Organizes code review into orientation, walkthrough, detail pass, and testing steps for commits, branches, PRs, or spec-driven changes.

1|Updated Dec 22, 2022
Search Tags:#testing#diff analysis#code review#checkpoint#risk assessment#walkthrough
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-checkpoint-preview-rinzler78
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-checkpoint-preview
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-checkpoint-preview
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-checkpoint-preview-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps a reviewer quickly understand a change, focus on the most important parts, and decide whether the implementation is ready to ship.

Core Features & Use Cases

  • Structured review workflow: Organizes review into orientation, walkthrough, detail pass, testing, and wrap-up.
  • Concern-based analysis: Groups code by design intent so reviewers can see what changed and why.
  • Risk and verification guidance: Highlights high-blast-radius areas and suggests ways to observe behavior manually.
  • Use Case: A developer shares a branch or PR, and you use this Skill to produce a clear, step-by-step review path before making a decision.

Quick Start

Ask the assistant to review the specified commit, branch, or PR and follow the checkpoint review workflow.

Frequently Asked Questions about bmad-checkpoint-preview

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

FAQPage Schema
How do I perform a structured code review for a pull request?▼

A structured code review organizes pull request changes into orientation, walkthrough, detail pass, and testing steps to help reviewers understand intent, surface risk, and validate behavior before shipping.

What is concern-based diff analysis in code review?▼

Concern-based diff analysis groups repository code changes by design intent so reviewers can see what changed and why, providing a clear step-by-step review path focused on high-blast-radius areas.

How do I assess risk and verify behavior in a commit diff?▼

Risk assessment and behavior verification highlight high-blast-radius areas within a commit diff and suggest manual ways to observe behavior, ensuring the implementation is ready to ship.

Can I use a checkpoint walkthrough for spec-driven branch changes?▼

Yes, a checkpoint walkthrough applies to spec-driven branch changes by reading repository diffs and code context to produce concern-based guidance and manual verification suggestions for human reviewers.

What is the best way to review repository diffs before shipping?▼

The best way to review repository diffs is a human-in-the-loop workflow that organizes changes into orientation, walkthrough, detail pass, testing, and wrap-up to decide whether the implementation is ready to ship.

Related Skills

Explore More Software Engineering Skills→
hanzlahabibhanzlahabib
2

rcode-checkpoint-preview

Guide a human through a five-step code change review before checkpoint approval.

Community
Advanced
RonHoubenRonHouben
2

merge-pull-request

Merge approved GitHub pull requests via GitHub CLI after CI checks pass.

Community
Intermediate
ccfccf

llm-evaluation

Automate LLM evaluation with automated metrics, human feedback, and benchmarking.

Community
Advanced
meteoricprovidermeteoricprovider
1

evaluate-ai-review-comments

Verify AI-generated pull request review comments for factual accuracy and contract alignment.

Community
Advanced