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"
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
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.
uv run --no-cache "{project-root}/_bmad/scripts/render_skill.py" --project-root "{project-root}" --skill "{skill-root}"HALT: <reason>: report the reason and stop.bmad skill, then run the command again. If you do not have the bmad skill, offer to install it first.uv being unavailable, report the command output and stop. Do not run any workflow source directly.bmad-code-org/BMAD-METHOD
61e01f8
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.