bmad-review

Invoke the review on the diff and the edge-case-hunter lens walks every branch and boundary condition, reporting only unhandled paths. Each finding includes the location, the missing condition, a guard snippet, and the potential consequence.

Five lenses ship by default: adversarial, edge-case-hunter, verification-gap, structure, and prose. The lens set is defined in customize.toml, so teams can add, replace, or disable lenses through override files.

Yes. Naming lenses in the request runs exactly those lenses, bypassing the applies_to and when filters. For example, asking for an editorial review runs only the structure and prose lenses on a document.

No. The verification-gap lens applies only to code reviewed inside a repository where tests can be searched and read. It checks whether changed behavior would actually fail an existing test if it regressed.

Set output_format in customize.toml to json, markdown, or both, and optionally set report_path to write the report to a file. Team and personal override TOML files merge with the shipped defaults.

An empty findings array is a valid result for most lenses, and the markdown report states the review is clean. The adversarial lens is the exception: it requires at least ten findings and treats an empty list as a signal to re-check.