Bmad Review
Runs one or more installed review lenses, adversarial critique, edge cases...
Install
npx skills add bmad-code-org/BMAD-METHOD --skill bmad-review -g -a claude-code -y- Repository
- bmad-code-org/BMAD-METHOD54.9k
- Category
- Git and review
- Updated
- 4d ago
- License
- See repository
- Context cost
- Mediumabout 2,281 tokens
- Runs scripts
- Yes, review before use
What it does
Runs one or more installed review lenses, adversarial critique, edge cases, verification gaps, structure, prose, and reports triaged findings. Use when, and only when, the user asks you to review a diff, a pull request, or an artifact, code or documents, one or many, and actually says "review"; an explicit skill:bmad-review directive from another skill counts as that ask. A request to act on feedback from an earlier review is a change, not a review. Never invoke this uninvited, including on edits you just made.
BMad Review
Review content through lenses, each a distinct method and stance, and report findings in one canonical shape. Report what is real, never pad to look thorough. Each lens sets its own stance toward the content and toward zero findings: for most an empty result is valid; the adversarial lens requires at least ten concrete findings and treats an empty list as a signal to re-check; the editorial lenses hold content sacrosanct and critique only how it is organized and expressed.
The lens set is whatever {workflow.lenses} resolves to, not a fixed list, overrides add lenses and replace shipped ones. Never claim a capability from this file; read the resolved lenses and work from those.
Inputs
- content, what to review: a diff, branch, uncommitted changes, file, ticket (initiative, epic, story, spike, bug), or any document. Args:
[path]. - lenses (optional), one or more lens codes or names, however the caller expresses them: a spoken request, or a directive of the form
skill:bmad-review lenses=<code>[,<code>...](the form bmm'sdoc_standardsuses). Default: every applicable lens (a full review). - also_consider (optional), areas to keep in mind alongside each lens's normal analysis.
- claims (optional), the change's own narrative: the commit messages it covers, or whatever description of it the caller supplied. Goes to the edge-case lens alone.
- pre-resolved customization (optional),
[workflow]field values supplied by a forwarding caller. See Execution step 1.

