bmad-code-review — Claude skill: parallel code review
This skill runs several independent reviewers in parallel, then triages their findings. Useful when you want changes checked before a merge.
npx skills add bmad-code-org/BMAD-METHOD --skill bmad-code-review -a claude-codeWhat bmad-code-review does
bmad-code-review comes from the BMAD-METHOD repo. It fans out your code changes to several independent reviewers at once, then collects and triages what they found. Trigger it with something like "run code review" or "review this code".
There is one step inside: the agent runs render_skill.py from _bmad/scripts/, the script prints the skill's workflow, and the agent follows it. Modes include quick and thorough (appended as --set workflow.review=), a no-code mode with --set workflow.fixes=handoff, and a non-interactive run via --set workflow.interactive=false for CI or a bot.
You need uv and BMad already set up in the project — the _bmad/ folder has to exist. If the script is missing, the skill offers to set BMad up first through the bmad skill. Install it if you already use BMAD-METHOD; otherwise you have to stand the method up first.
What it helps with
- run changes past several reviewers at once
- collect review notes into one list
- run a review with no prompts inside CI
- pick between a quick and a thorough pass
- hand fixes off to a separate step
Example prompts for the agent
- run code review
- review this code, quick
- do a thorough review of these changes
How to install bmad-code-review
1Skills CLI (Vercel)
npx skills add bmad-code-org/BMAD-METHOD --skill bmad-code-review -a claude-code2Manually: put the files in place
~/.claude/skills/bmad-code-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/bmad-code-review/
1Skills CLI (Vercel)
npx skills add bmad-code-org/BMAD-METHOD --skill bmad-code-review -a codex2Manually: put the files in place
.agents/skills/bmad-code-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add bmad-code-org/BMAD-METHOD --skill bmad-code-review -a cursor2Manually: put the files in place
.cursor/skills/bmad-code-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install bmad-code-org/BMAD-METHOD bmad-code-review2Manually: put the files in place
.github/skills/bmad-code-review/SKILL.md1Skills CLI (Vercel)
npx skills add bmad-code-org/BMAD-METHOD --skill bmad-code-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/bmad-code-org/BMAD-METHOD --path skills/bmad-code-reviewManually: put the files in place
.devin/skills/bmad-code-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add bmad-code-org/BMAD-METHOD --skill bmad-code-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set25
The whole set →Similar
Questions about bmad-code-review
How do I install bmad-code-review in Claude?
Run npx skills add bmad-code-org/BMAD-METHOD --skill bmad-code-review -a claude-code. The skill lands at ~/.claude/skills/bmad-code-review/SKILL.md.
What does bmad-code-review do?
It runs several independent reviewers in parallel, then triages and presents their findings on your code changes.
What does the skill need to run?
uv plus BMad set up in the project — the _bmad/ folder with scripts/render_skill.py. Without them the skill offers to install BMad first.
Source text
SKILL.md · MIT
---
name: bmad-code-review
description: 'Review code changes with several independent reviewers in parallel, then triage and present the findings. Use when the user says "run code review" or "review this code"'
---
Run the following command exactly once without changing the current working directory.
Replace `{project-root}` with the nearest folder containing `_bmad/`, from the working directory upward.
Replace `{skill-root}` with the absolute path to this skill's directory.
If the invocation asks for a `quick` or `thorough` review, append `--set workflow.review=<value>` to the command.
If the invocation asks for a `no-code` review, append `--set workflow.fixes=handoff` to the command.
If the invocation is clearly non-interactive -- it says not to ask questions, or a bot, a CI job or another workflow is running the review -- append `--set workflow.interactive=false`. When in doubt, don't.
```bash
uv run --no-cache "{project-root}/_bmad/scripts/render_skill.py" --project-root "{project-root}" --skill "{skill-root}"
```
- The command prints the skill's workflow: follow it. `HALT: <reason>`: report the reason and stop.
- If the script does not exist, BMad is not set up in this project yet. Offer to set it up using `bmad` skill, then run the command again. If you do not have the `bmad` skill, offer to install it first.
- On any other output or failure, including `uv` being unavailable, report the command output and stop. Do not run any workflow source directly.
© bmad-code-org · MIT · bmad-code-org/BMAD-METHOD