bmad-code-review

Trigger the workflow by asking to run a code review, then choose a diff source such as uncommitted changes, staged changes, a branch diff, or a commit range. The Skill constructs the git diff, launches parallel review layers, and triages the findings.

It uses three parallel layers: a Blind Hunter that sees only the diff, an Edge Case Hunter with project read access, and an Acceptance Auditor that checks the diff against a spec file. The Acceptance Auditor is skipped when no spec is provided.

Yes, select the branch diff option and specify the base branch. The Skill verifies the base branch exists before running git diff, and halts to ask for a valid branch if it does not.

Findings are classified as decision-needed, patch, defer, or dismiss. Decision-needed items require your input, patches can be auto-applied or left as action items, and deferred items are logged to a deferred-work file.

Yes, when a story file and story key are available, the Skill updates the story status to done or in-progress and syncs the matching entry in sprint-status.yaml. If no story key exists, only the story file is updated.

The failed layer is recorded in a failed_layers list and the review proceeds with the remaining layers. If zero findings remain and any layer failed, the Skill warns that the review may be incomplete instead of declaring it clean.