bmad-review

Reviews diffs, pull requests, and documents through configurable lenses and reports triaged findings.

Updated Sep 4, 2026
One-click install
npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-review-joao-victor-medeiros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-review
Source: https://github.com/Joao-Victor-Medeiros/save-sc/tree/main/.agents/skills/bmad-review
Command: npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-review-joao-victor-medeiros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Reviewing code changes and documents consistently is hard: reviewers miss edge cases, skip verification checks, or apply inconsistent standards. This Skill runs structured review passes — adversarial critique, edge-case tracing, verification-gap analysis, and editorial structure/prose review — and reports findings in one canonical shape. ## Core Features & Use Cases - Multi-lens review: Runs adversarial, edge-case-hunter, verification-gap, structure, and prose lenses, each with its own method and findings shape, selected automatically by content type or explicitly by the caller. - Customizable workflow: A customize.toml file plus team/user override files control lenses, style guides, output format, standing review directives, and report destinations. - Parallel subagent execution: Independent lenses can run simultaneously as subagents, with dependent lenses (like prose after structure) chained on prior findings. - Use Case: Ask for a review of a pull request diff; the Skill stages the diff, runs the applicable lenses, and returns a JSON findings array plus a markdown report grouped by lens with concrete fixes and consequences. ## Quick Start Ask the assistant to review the current branch diff or a specific file, for example: review the uncommitted changes in this repository.

Frequently Asked Questions about bmad-review

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

FAQPage Schema
How do I review a pull request or diff with multiple review lenses?▼

Invoke the review on a diff, branch, or uncommitted changes and it stages the content as a file, selects applicable lenses, and runs them. Findings come back as a JSON array with location, trigger condition, guard snippet, and potential consequence, plus an optional markdown report.

What review lenses are available for code and document review?▼

Five lenses ship by default: adversarial critique, edge-case hunting, verification-gap analysis for code, and structure plus prose editorial passes for documents. Lenses are defined in customize.toml and can be replaced or extended with team or user override files.

Can I customize the review style guide and output format?▼

Yes, customize.toml sets the style guide (defaulting to the Microsoft Writing Style Guide), reader type, output format (json, markdown, or both), report path, and standing review directives. Team and user override TOML files merge over the shipped defaults.

When should I not trigger an automated review?▼

Only run it when the user explicitly asks for a review of a diff, pull request, or artifact. A request to act on earlier review feedback is a change request, not a review, and the Skill must never be invoked uninvited on edits just made.

Does the edge-case review check commit message claims?▼

Yes, when a claims file is provided, the edge-case lens reads it only after finishing path tracing, then tries to falsify each checkable claim against the traced code. Falsified claims are reported as findings with a confidence rating.