bmad-code-review

Coordinate adversarial code review across branches, diffs, and pull requests.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AhmedKaram50/research --skill bmad-code-review-ahmedkaram50
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-code-review
Source: https://github.com/AhmedKaram50/research/tree/main/shopify-builder/_bmad/bmm/workflows/4-implementation/bmad-code-review
Command: npx skills add https://github.com/AhmedKaram50/research --skill bmad-code-review-ahmedkaram50

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews can be lengthy and inconsistent. This skill coordinates adversarial, multi-layer reviews to surface issues early and deliver actionable triage.

Core Features & Use Cases

  • Parallel review layers: Blind Hunter, Edge Case Hunter, and Acceptance Auditor run in concert to diversify perspectives.
  • Structured triage: Findings are categorized and actionable for fast remediation.
  • Workflow automation: Step-file driven, deterministic execution with checkpoints and clear requirements.

Quick Start

Invoke the code review workflow by supplying the code changes you want reviewed and triggering the parallel review layers.

Frequently Asked Questions about bmad-code-review

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

FAQPage Schema
What is an adversarial code review workflow for pull requests?

An adversarial code review workflow for pull requests coordinates parallel review layers, such as a Blind Hunter and an Edge Case Hunter, to surface diverse perspectives and produce structured, actionable triage findings.

How do I automate code review triage for branch diffs?

Automate code review triage for branch diffs by invoking a step-file driven workflow that constructs diffs, loads specifications, and runs parallel review layers to output categorized, actionable findings for remediation.

Can I use a multi-layer code review process without any external dependencies?

Yes, you can run this multi-layer code review process without external dependencies, as it operates independently to coordinate parallel reviews and generate structured triage directly from your code changes.

What is the best way to find edge cases in a code diff before merging?

The best way to find edge cases in a code diff is to deploy an Edge Case Hunter layer within an adversarial review workflow, systematically diversifying perspectives to surface hidden issues early.

Does the Acceptance Auditor check code changes against project specifications?

Yes, the Acceptance Auditor checks code changes against project specifications by loading spec documents during the triage pipeline to ensure the implementation meets the defined acceptance criteria.

Why should I use a step-file driven workflow for code reviews?

Use a step-file driven workflow for code reviews to enforce strict initialization, deterministic execution, and clear checkpoints, ensuring consistent, structured findings rather than lengthy, inconsistent manual reviews.