bmad-review

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

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

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 hunting, verification-gap analysis, and editorial structure/prose review — and returns findings in one canonical format. ## Core Features & Use Cases - Multi-lens review: Runs adversarial, edge-case, verification-gap, structure, and prose lenses, each with its own method and stance, selectable per run. - Canonical findings output: Every finding carries location, trigger condition, concrete fix, and potential consequence, emitted as JSON, markdown, or both. - Customizable workflow: A customize.toml file plus team/user override files control lenses, style guides, review guidance, output format, and report destination. - Use Case: Ask for a review of an open pull request; the Skill stages the diff, runs the applicable lenses (in parallel subagents when available), and delivers a triaged findings report grouped by lens. ## 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 critique lenses?

Ask for a review of the diff, branch, or uncommitted changes. The Skill stages the content as a file, selects applicable lenses (adversarial, edge-case, verification-gap, structure, prose), runs them, and returns findings with location, trigger condition, fix, and consequence.

What review lenses are available for code and document review?

Five shipped lenses: adversarial (finds at least ten issues), edge-case hunter (exhaustive path tracing), verification-gap (test coverage of changed behavior), structure (document organization), and prose (copy-editing). Overrides in customize.toml can add or replace lenses.

Can I customize the review lenses and output format?

Yes. The customize.toml workflow table controls lenses, output format (json, markdown, or both), report path, style guide, reader type, and standing review guidance. Team and personal override files merge per BMad structural rules.

When should I not trigger an automated review pass?

Only invoke it when a review is explicitly requested. Acting on feedback from an earlier review is a change, not a review, and the Skill must never run uninvited on edits just made.

Does the edge-case review check claims in commit messages?

Yes. When a claims file is provided, the edge-case lens reads it only after path tracing completes, then tries to falsify each checkable claim against the traced code, reporting contradictions with a confidence rating.