bmad-bmm-code-review

Execute adversarial code reviews using fixed internal workflow files.

1|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/LucaDeLeo/ASTN --skill bmad-bmm-code-review-lucadeleo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-bmm-code-review
Source: https://github.com/LucaDeLeo/ASTN/tree/main/.agents/skills/bmad-bmm-code-review
Command: npx skills add https://github.com/LucaDeLeo/ASTN --skill bmad-bmm-code-review-lucadeleo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perform adversarial code review to identify issues in codebases by enforcing a defined internal workflow.

Core Features & Use Cases

  • Guided, deterministic code reviews using the internal workflow.xml and code-review workflow.yaml to ensure consistent findings.
  • Automatic enforcement of the prescribed steps and per-section output saving to preserve traceability.
  • Use Case: When a code change needs rigorous security and robustness validation before merge.

Quick Start

Instruct the AI to begin a code review by loading the full internal workflow and executing the designated code-review workflow.

Frequently Asked Questions about bmad-bmm-code-review

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

FAQPage Schema
How do I run an adversarial code review to find security issues in my codebase?

Adversarial code review identifies specific security and robustness issues by loading a fixed internal workflow. You trigger it by instructing the AI to execute the designated code-review workflow, ensuring consistent findings and per-section output saving for traceability.

What is an adversarial code review and how does its workflow function?

Adversarial code review is a deterministic process that applies strict workflow rules to find codebase issues. It functions by loading a configured workflow.yaml and executing prescribed steps, automatically saving outputs to preserve validation traceability.

How do I ensure my code changes pass rigorous security validation before a merge?

Rigorous security validation before merge requires running a guided, deterministic code review. By enforcing a prescribed internal workflow, the review identifies vulnerabilities and ensures robustness checks are consistently applied to your code sample.

Does this code review workflow require specific configuration files to run?

The code review workflow requires specific configuration files to run. It enforces a fixed workflow via {project-root}/_bmad/core/tasks/workflow.xml and the code-review workflow at {project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml.

Can I trigger a code analysis automatically or do I need explicit commands?

Code analysis is triggered by explicit review commands such as "run code review" or when actively reviewing a code sample. This explicit activation ensures the strict adversarial workflow executes only when rigorous validation is required.

What are the limitations of using a fixed workflow for code analysis?

A fixed workflow for code analysis limits flexibility by enforcing prescribed steps and strict per-section output saving. This deterministic approach prioritizes consistency and traceability over adaptable, free-form code review strategies.