skills.rest
mol4
mol4COMMUNITY
Explore all skills by this author →
GitHub

bmad-code-review

Review BMAD code changes with adversarial analysis and triage findings.

1|Updated Mar 31, 2026
Search Tags:#diff analysis#code review#triage#bmad#sprint tracking#acceptance audit
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-code-review-mol4
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-code-review
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-code-review
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-code-review-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you perform disciplined, adversarial code reviews on BMAD project changes so defects, edge cases, and spec mismatches are caught before merge.

Core Features & Use Cases

  • Parallel review layers: Uses Blind Hunter, Edge Case Hunter, and Acceptance Auditor perspectives to uncover different classes of problems.
  • BMAD-aware triage: Deduplicates findings and classifies them into patch, defer, dismiss, or decision-needed so the output is easy to act on.
  • Workflow integration: Reads diffs, story files, and sprint status, then writes findings back into the project’s review workflow when needed.
  • Use case: Review a branch, commit range, staged changes, or a provided diff and get a structured report of risks, fixes, and deferred issues.

Quick Start

Ask the bmad-code-review skill to review the changes in my current branch against main and use the relevant story file for context.

Frequently Asked Questions about bmad-code-review

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

FAQPage Schema
How do I perform an adversarial code review on a branch diff before merge?▼

To perform an adversarial code review on a branch diff, you can use parallel analysis layers that hunt for blind spots, edge cases, and acceptance mismatches. The process reads your branch changes and triages findings into actionable categories like patch or defer.

What is the best way to triage code review findings for sprint tracking?▼

Triage code review findings by deduplicating issues and classifying them into patch, defer, dismiss, or decision-needed categories. This structured approach ensures sprint tracking remains clear and only actionable risks are written back into the project workflow.

How does code review integration work with BMAD story files?▼

BMAD story file integration works by reading the story file for context during the review and writing the triaged findings back into the project's review workflow. This synchronizes sprint status and ensures code changes align with story acceptance criteria.

Can I audit code changes against acceptance criteria automatically?▼

You can audit code changes against acceptance criteria using the Acceptance Auditor perspective. This parallel review layer specifically checks your diffs and commits for spec mismatches to ensure the implementation meets the defined requirements.

Related Skills

Explore More Software Engineering Skills→
diegosanchespereira1diegosanchespereira1

bmad-code-review

Review code diffs for defects, edge cases, and spec mismatches.

Community
Advanced
amitmishra-bylddamitmishra-byldd

bmad-code-review

Review code diffs adversarially and triage findings into actionable categories.

Community
Advanced
ravensorbravensorb

l3io-pm-sprint-execute

Orchestrate sprint lifecycle stages with BMad subagents and quality gates.

Community
Advanced
ahiendzahiendz
3

lint-and-validate

Lint and statically analyze Node.js/TypeScript and Python codebases.

Community
Intermediate