bmad-code-review

Reviews code changes adversarially using parallel review layers and structured triage.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-code-review-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-code-review
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-code-review
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-code-review-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code reviews often miss edge cases, verification gaps, and spec deviations because a single reviewer pass lacks diverse perspectives. This Skill runs multiple adversarial review layers in parallel over a diff, then triages findings into actionable buckets so real issues get fixed and noise gets dismissed. ## Core Features & Use Cases - Parallel Review Layers: Runs Blind Hunter, Edge Case Hunter, Verification Gap, and Acceptance Auditor subagents against the same diff for independent perspectives. - Structured Triage: Deduplicates findings, verifies them against actual source code, assigns severity, and routes each into decision-needed, patch, defer, or dismiss buckets. - Sprint Integration: Writes findings into story files, syncs sprint-status.yaml, and supports customizable workflow overrides via TOML configuration. - Use Case: After finishing a feature branch, ask for a code review; the Skill gathers the diff, runs all review layers, presents triaged findings, and applies approved patches. ## Quick Start Ask the assistant to run a code review on your current uncommitted changes or a specific branch diff.

Frequently Asked Questions about bmad-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an adversarial code review on my changes?

Invoke the skill with a review target such as uncommitted changes, a branch diff, a commit range, or a PR reference. The workflow gathers the diff, runs parallel review layers, triages findings, and lets you approve patches.

What review layers does this code review workflow use?

It runs four layers: Blind Hunter for general issues, Edge Case Hunter for unhandled paths, Verification Gap for missing test coverage, and Acceptance Auditor for spec compliance. Layers can be customized or disabled via TOML overrides.

Can I customize the code review workflow steps?

Yes, customization is done through customize.toml and project-level override files that merge structurally. You can add activation steps, persistent facts, modify review layer instructions, and set an on_complete action.

Does the code review work without a spec file?

Yes, it supports a no-spec review mode where spec-dependent layers like Acceptance Auditor are skipped. Findings that would need a decision are reclassified as patch or defer instead.

What happens if a review subagent fails or returns nothing?

Failed or empty layers are recorded in a failed_layers list and the review proceeds with remaining layers. If no findings remain and layers failed, the workflow warns that the review may be incomplete rather than declaring it clean.