bmad-walkthrough

Guides human reviewers through code changes with orientation, risk analysis, and testing suggestions.

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill bmad-walkthrough-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-walkthrough
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/bmad-walkthrough
Command: npx skills add https://github.com/PastaSus/egg-defender --skill bmad-walkthrough-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a code change without context is slow and error-prone. This Skill walks a human reviewer through a change step by step — what it is for, which code locations matter most, where the risks are, and how to observe the behavior — so review decisions are grounded in the actual diff. ## Core Features & Use Cases - Guided Review Trail: Builds a concern-based walkthrough from a spec's Suggested Review Order or generates one from the git diff, with clickable path:line stops. - Risk Spot Detection: Surfaces high blast-radius changes across auth, schema, billing, security, config, and public API categories without assigning severity scores. - Manual Testing Suggestions: Proposes concrete actions and expected observable results for UI, CLI, API, and state changes. - Use Case: After a teammate opens a PR for an auth refactor, trigger the walkthrough to get the intent summary, surface-area stats, an ordered review trail, risk spots like token validation changes, and commands to verify the new behavior before approving. ## Quick Start Ask the assistant to walk you through the current branch or a specific PR for human review.

Frequently Asked Questions about bmad-walkthrough

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

FAQPage Schema
How do I review a pull request with a guided walkthrough?

Pass a PR reference, commit SHA, or branch when triggering the walkthrough. It resolves the change via gh pr view or git, summarizes the intent, computes diff stats, and presents an ordered trail of path:line stops grouped by design concern.

What happens if there is no spec or review order for a change?

The skill generates a review trail from the git diff by reading changed files in full, identifying 2-5 cohesive design concerns, and selecting path:line stops for each. If git is unavailable, it falls back to a non-trail walkthrough mode.

How does the detail pass decide which risk spots to show?

It scans the diff for risk-sensitive patterns such as auth, public API, schema, billing, infra, security, and config changes, then orders up to 5 spots by blast radius. If nothing matches, it states that explicitly rather than inventing findings.

Can I dig deeper into one area during the review?

Yes. Saying "dig into [area]" triggers a targeted re-review that reads the relevant diff locations in full context and checks edge cases, boundary conditions, error handling, and race conditions, then reports findings as a compact list.

Does the walkthrough approve PRs automatically?

No. The final step asks the human to choose approve, rework, or discuss. It only offers to run gh pr review --approve after explicit confirmation, since that is a visible action on a shared resource.