bmad-review

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

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

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, and 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 with team and user overrides controls lenses, style guides, output format, standing review directives, and report destinations. - Parallel subagent execution: Independent lenses run simultaneously as subagents when available, 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 locations, 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, fix, and consequence, plus an optional markdown report.

What review lenses are available for code and documents?

Five lenses ship by default: adversarial critique, edge-case path tracing, verification-gap analysis for code, and structure plus prose editing for documents. Lenses are keyed by code in customize.toml, so teams can replace shipped lenses or add their own.

Can I customize the review style guide and output format?

Yes, team and user override TOML files merge over the shipped customize.toml. You can set the style guide, reader type, output format (json, markdown, or both), report path, standing review directives, and activation steps.

Does the edge-case review check commit message claims against the code?

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. Falsified claims become findings with a confidence rating.

When should I not trigger this review skill?

Do not invoke it uninvited, including on edits just made, and do not use it to act on feedback from an earlier review — that is a change request, not a review. It runs only when the user explicitly asks for a review of a diff, pull request, or artifact.