skills.rest
Asygnuz-S-A-S
Asygnuz-S-A-SOFFICIAL
Explore all skills by this author →
GitHub

bmad-code-review

Reviews code changes with parallel adversarial layers and structured triage into actionable findings.

Updated May 22, 2026
Search Tags:#workflow#code review#subagents#triage#sprint#git diff#adversarial review
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-code-review-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-code-review
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-code-review
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-code-review-asygnuz-s-a-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual code reviews often miss edge cases, lack consistency, and produce unstructured feedback that is hard to act on. This Skill runs adversarial multi-layer reviews of git diffs and converts findings into triaged, actionable items. ## Core Features & Use Cases - Parallel Review Layers: Runs three independent reviewers — a Blind Hunter (diff only), an Edge Case Hunter (diff plus project access), and an Acceptance Auditor (diff against a spec file). - Structured Triage: Normalizes, deduplicates, and classifies findings into decision-needed, patch, defer, or dismiss buckets. - Sprint Integration: Writes findings into story files, updates story status, and syncs sprint-status.yaml after the review. - Use Case: After finishing a story branch, ask for a code review; the Skill gathers the diff, launches the review layers, presents triaged findings, and applies approved patches. ## Quick Start Ask the assistant to run a code review on the current branch diff against main.

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 a git diff?▼

Provide a diff source such as a branch, commit range, staged changes, or a pasted diff. The workflow launches parallel review layers — Blind Hunter, Edge Case Hunter, and Acceptance Auditor — then triages their findings into actionable categories.

What diff sources does this code review workflow support?▼

It supports uncommitted changes, staged-only changes, branch diffs against a base branch, specific commit ranges, user-pasted diffs, and explicit file lists. It validates each source and halts if the diff is empty or unparseable.

Can code review findings be written back to a story file?▼

Yes. When a spec or story file is provided, findings are appended as a Review Findings section with decision, patch, and defer items. The story status and sprint-status.yaml are updated based on the review outcome.

What happens if a review subagent fails or returns nothing?▼

The failed layer name is recorded and the review proceeds with the remaining layers. If all findings end up empty while layers failed, the workflow warns that the review may be incomplete instead of declaring it clean.

Does the review work without a spec file?▼

Yes, it runs in no-spec mode where the Acceptance Auditor layer is skipped. Findings that would require a decision are reclassified as patch or defer since no acceptance criteria exist to resolve ambiguity.

Related Skills

Explore More Software Engineering Skills→
MathematicGuyMathematicGuy

bmad-code-review

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

Community
Advanced
SevWrenSevWren
1

bmad-dev-story

Implements sprint stories from spec files using red-green-refactor cycles and definition-of-done validation.

Community
Advanced
uzumaki-incuzumaki-inc

health

Run code health checks and compute a weighted 0-10 score.

Official
Advanced
basicmachines-cobasicmachines-co
4.0k

fix-pr-issues

Resolves pull request feedback and failed checks, then re-runs the Codex review gate.

Official
Intermediate