bmad-walkthrough
From the author
Guide a human review of a commit, PR, file, or directory. Use when invoked by name
Install
npx skills add alvin-reyes/better-agentic-ide --skill bmad-walkthrough -a claude-code
Installs to .claude/skills/bmad-walkthrough/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
Security100
Provenance63
Maintenance100
Licence100
Adoption34
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- review-walkthroughtrailofbits/skillsGenerates an interactive HTML walkthrough for reviewing code changes. Use only when explicitly called.Engineering★ 7.8K
- bmad-buildalvin-reyes/better-agentic-ideTurns implementation work into working code, reviewed and verified. Use when the user delegates a feature, story, bug fix, or meaningful change; a bare story or issue link counts. Skip obvious, low-risk mechanical maintenance such as small ignore-file, typo-only, formatting-only, or configuration-hygiene edits. Explicit BMAD requests always qualify. Do not volunteer for user-directed interactive edits or version-control operations that only record existing work.Writing★ 85
- bmad-prdalvin-reyes/better-agentic-ideCreate, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRDPlanning★ 85
- code-walkthroughtestdouble/hanWalks a person through code changes one step at a time in conversation, starting at the entry point and following the flow that changes, showing a small chunk per step and explaining it in plain language. Defaults to the current branch's changes, and walks the code from the perspective of any context provided instead — a file, directory, symbol, pull request, plan, or ticket. Use when someone wants to be walked through, taught, paced through, or shown around code or a branch step by step, or to learn how a change works before reviewing or extending it. Stops after every step and waits, so the learner sets the pace. Paces through code that already exists and builds nothing — to build new work while being paced through it, use pairing. Does not produce a written overview to read alone — use code-overview. Does not review code quality — use code-review. Does not diagnose bugs — use investigate.Engineering★ 323
- bmadalvin-reyes/better-agentic-ideAnswers BMad questions and recommends the next skill from what is installed. Use when the user asks bmad for help, what to do next or where to start; to set up, update, repair, doctor, migrate or check the status of the installation, or add modules; or to see or change the active initiative.Other★ 85
- reviewhashgraph-online/awesome-codex-pluginsGive advisory feedback on a plan, design or code change. Use when: asked for an opinion or a look-over, even informally. Not for acceptance; use Validate.Engineering★ 1.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in