bmad-code-review

Review code diffs for bugs, edge cases, and spec violations.

1|Updated Dec 22, 2022
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-code-review-rinzler78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-code-review
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-code-review
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-code-review-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you review code changes thoroughly and adversarially so bugs, edge cases, and spec mismatches are caught before merge.

Core Features & Use Cases

  • Parallel review layers: Runs a Blind Hunter, Edge Case Hunter, and Acceptance Auditor to surface different classes of issues.
  • Structured triage: Deduplicates findings and classifies them into patch, defer, decision-needed, or dismiss.
  • Spec-aware validation: Compares diffs against story/spec context when available and writes actionable findings back to the review file.
  • Workflow control: Guides the review through context gathering, triage, presentation, and follow-up actions with clear checkpoints.

Quick Start

Ask the assistant to run a code review on a specific diff, branch, or commit range.

Frequently Asked Questions about bmad-code-review

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

FAQPage Schema
How do I review a pull request diff for edge cases and spec violations?

Review a pull request diff by running adversarial multi-layer analysis that hunts for blind spots, edge cases, and acceptance criteria mismatches against provided spec files, then triages findings into structured categories for actionable resolution.

What is the best way to triage code review findings before merging a branch?

Triage code review findings by deduplicating detected issues and classifying them into patch, defer, decision-needed, or dismiss categories, providing structured workflow control with clear checkpoints from context gathering through final presentation.

Can I use diff analysis on uncommitted or staged changes?

Diff analysis applies to staged changes, uncommitted diffs, branches, and commit ranges, allowing you to review code changes thoroughly and catch bugs before merge regardless of the development workflow state.

How does spec-aware code validation work with story context?

Spec-aware code validation compares diffs against story or spec files when available, writing actionable findings back to the review file to ensure code changes align with acceptance criteria before they ship.

Do I need spec files to run a code review on a commit range?

Spec files are optional for running a code review on a commit range; the review workflow requires diff context but can operate without spec validation, focusing instead on bug detection and edge case analysis.

What classes of issues does adversarial code review catch that standard reviews miss?

Adversarial code review catches hidden bugs, unhandled edge cases, and spec mismatches by running parallel analysis layers including a Blind Hunter, Edge Case Hunter, and Acceptance Auditor to surface different classes of issues before merge.