bmad-code-review

Run adversarial code review on a git diff by triggering a multi-layer workflow that analyzes changes through Blind Hunter, Edge Case Hunter, and optional Acceptance Auditor perspectives. You get structured, triaged findings categorized for decision, patch, defer, or dismissal.

Adversarial code review applies multiple analytical perspectives to branch diffs to actively hunt for defects and boundary-condition bugs. It uses a Blind Hunter for diff-only issues and an Edge Case Hunter with project read access to find integration problems and edge cases.

Yes, validate staged or uncommitted changes against acceptance criteria using the Acceptance Auditor. When you provide a spec, it loads context docs, checks changes against requirements, and highlights missing or contradictory behavior in the diff.

Triage code review findings by normalizing adversarial analysis results into actionable categories. The workflow groups issues into decision-needed, patchable, deferred, and dismissed buckets so you can manage pull request changes clearly.

Adversarial code review works with commit ranges, provided diffs, and file lists. You can review changes with optional spec context, applying the multi-layer review workflow to surface defects, edge cases, and spec mismatches across any provided diff or commit range.

The best way to catch spec mismatches is running the Acceptance Auditor workflow with a provided spec. It validates code changes against loaded context docs and acceptance criteria, highlighting any missing or contradictory behavior before shipping.