bmad-code-review

Yes, you can validate staged and uncommitted changes against a spec by applying the Acceptance Auditor layer, which checks findings against acceptance criteria and context docs before persisting them into the story file.

To triage code review findings, the workflow normalizes, deduplicates, and classifies adversarial review results into decision_needed, patch, defer, or dismiss categories, guiding user-gated next actions and patch-handling steps.

Adversarial testing on a commit range is best performed by constructing a diff from the range and invoking parallel review layers to hunt for edge cases and blind spots, resulting in deterministic triage of discovered vulnerabilities.

Yes, you can use spec validation to check pull request diffs by running the Acceptance Auditor, which validates diff findings against provided spec context and context docs, then persists the results into the story file.

Without a provided spec, automated code review limitations include skipping the Acceptance Auditor layer, limiting the validation to blind and edge case hunting without structured acceptance criteria checking or story file persistence.