bmad-walkthrough

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

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-walkthrough-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-walkthrough
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/bmad-walkthrough
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-walkthrough-archaonhw

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 its intent, to a concern-organized walkthrough, to risk-spot detection, to hands-on verification — so the review decision is informed rather than rubber-stamped. ## Core Features & Use Cases - Orientation and Intent Summary: Identifies the change from a PR, commit, branch, spec, or sprint status, then summarizes intent and surface-area stats (files changed, modules touched, boundary crossings). - Concern-Based Walkthrough: Groups diff stops by design intent rather than by file, ordered for comprehension with clickable path:line references. - Risk and Testing Passes: Surfaces high-blast-radius spots (auth, schema, billing, security, config) and suggests manual observations of user-visible behavior, ending in an approve/rework/discuss decision. - Use Case: After a teammate opens a PR, ask for a walkthrough — the Skill resolves the diff baseline, builds a review trail, and guides you through each concern before you approve via gh pr review. ## Quick Start Ask the assistant to walk you through the current change or a specific PR, for example by saying "walk me through this change on the current branch".

Frequently Asked Questions about bmad-walkthrough

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

FAQPage Schema
How do I walk through a code change before approving a PR?

Invoke the walkthrough with a PR reference, commit SHA, or branch name. The Skill resolves the diff baseline, summarizes intent and surface-area stats, then guides you through concerns, risk spots, and testing suggestions before you decide.

How does the walkthrough decide what change to review?

It checks in order: an explicit 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 and halts after three unresolved exchanges.

Can the walkthrough work without a spec or review trail?

Yes. If no spec with a Suggested Review Order exists, it generates a review trail from the diff by reading changed files and grouping 2-5 concerns with path:line stops. If git is unavailable, it falls back to a non-trail mode.

Does the walkthrough approve pull requests automatically?

No. It can offer to run gh pr review --approve, but only after you explicitly choose Approve and confirm, since approving is a visible action on a shared resource.

What risk categories does the detail pass detect?

It scans the diff for auth, public API, schema, billing, infra, security, and config changes, plus a catch-all category for concerns like concurrency or backwards compatibility. Spots are ordered by blast radius, capped at five.

What are the limitations of the walkthrough review?

It depends on git for diffs and stats, so it degrades when git is unavailable. It also does not replace CI or automated tests — its testing step only suggests manual observations of user-visible behavior.