bmad-review
Skill1 starsChanged 16 days agoApache-2.0View on GitHub
Runs one or more installed review lenses — adversarial critique, edge cases, verification gaps, structure, prose — and reports triaged findings. Use when, and only when, the user asks you to review a diff, a pull request, or an artifact — code or documents, one or many — and actually says "review"; an explicit skill:bmad-review directive from another skill counts as that ask. A request to act on feedback from an earlier review is a change, not a review. Never invoke this uninvited, including on edits you just made.
9 other projects use a version of this, 7 of them edited.
Adopted by
Most recently taken up by
- bmad-code-org/BMAD-METHODedited, first seen Nov 15, 2026
- snovak7/bmad-github-zoho-pipelineedited, first seen Nov 14, 2026
- delorenj/skillsword for word, first seen Nov 7, 2026
- salacoste/daytona-seo-notchedited, first seen Nov 1, 2026
- MysterionRise/forgetestedited, first seen Oct 25, 2026
- alvin-reyes/better-agentic-ideedited, first seen Oct 17, 2026
Used with
Projects with it also use bmad.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
magnus919Skillbmad
Use this skill to run BMad (Breakthrough Method of Agile AI-Driven Development) as a harness-agnostic control-plane protocol that turns human intent into bounded, inspectable, resumable agent work. Compress intent into a five-field contract (Why, Capabilities, Constraints, Non-goals, Success signal); classify work as direct/bounded/initiative and route to the smallest safe path; carry decisions in durable artifacts; review as triage; route failure to the layer where ambiguity entered; and gate autonomy on observable acceptance with machine-readable status (draft/ready-for-dev/in-progress/in-review/done/blocked). Use when a change request, feature, delegated build, or multi-agent epic needs intent capture, bounded implementation, review, and resumability in any agent harness. Do not use for validating whether a problem is real (product-discovery), shaping bets before planning (product-shaping), formal spec/gate pipelines (spec-driven-development), or the issue-to-PR delivery flow (neckbeard).
Also in 3 projects that use this
Other versions9 projects use a version of this.
Word for word · 2
- delorenj/skills★ 17100% same
- salacoste/oh-my-bmad★ 2100% same
Edited · 7
- bmad-code-org/BMAD-METHOD★ 55k94% same
- alvin-reyes/better-agentic-ide★ 4394% same
- 2233admin/opencli-Razormind★ 1991% same
- MysterionRise/forgetest★ 491% same
- mannnrachman/pi-bmad★ 2100% same
- salacoste/daytona-seo-notch★ 094% same
- snovak7/bmad-github-zoho-pipeline★ 091% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository157 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bmad-advanced-elicitationSkill
- bmad-agent-analystSkill
- bmad-agent-architectSkill
- bmad-agent-builderSkill
- bmad-agent-devSkill
- bmad-agent-pmSkill
- bmad-agent-ux-designerSkill
- bmad-architectureSkill
- bmad-bmb-setupSkill
- bmad-brainstormingSkill
- bmad-build-autoSkill
- bmad-buildSkill
- bmad-checkpoint-previewSkill
- bmad-cis-agent-brainstorming-coachSkill
- bmad-cis-agent-creative-problem-solverSkill
- bmad-cis-agent-design-thinking-coachSkill
- bmad-cis-agent-innovation-strategistSkill
- bmad-cis-agent-presentation-masterSkill
- bmad-cis-agent-storytellerSkill
- bmad-cis-design-thinkingSkill
- bmad-cis-innovation-strategySkill
- bmad-cis-problem-solvingSkill
- bmad-cis-storytellingSkill
- bmad-code-reviewSkill
- bmad-correct-courseSkill
- bmad-create-architectureSkill
- bmad-create-epics-and-storiesSkill
- bmad-create-prdSkill
- bmad-create-storySkill
- bmad-customizeSkill
- bmad-deep-reconSkill
- bmad-dev-autoSkill
- bmad-dev-storySkill
- bmad-document-projectSkill
- bmad-domain-researchSkill
- bmad-editorial-review-proseSkill
- bmad-editorial-reviewSkill
- bmad-editorial-review-structureSkill
- bmad-edit-prdSkill
- bmad-eval-runnerSkill
- bmad-forge-ideaSkill
- bmad-generate-project-contextSkill
- bmad-helpSkill
- bmad-loop-resolveSkill
- bmad-loop-setupSkill
- bmad-loop-sweepSkill
- bmad-market-researchSkill
- bmad-module-builderSkill
- bmad-party-modeSkill
- bmad-prdSkill
- bmad-prfaqSkill
- bmad-product-briefSkill
- bmad-project-contextSkill
- bmad-qa-generate-e2e-testsSkill
- bmad-quick-devSkill
- bmad-retrospectiveSkill
- bmad-review-adversarial-generalSkill
- bmad-review-edge-case-hunterSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 50
When {workflow.report_path} is set, write the report there.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
BMad Review
Review content through lenses — each a distinct method and stance — and report findings in one canonical shape. Report what is real — never pad to look thorough. Each lens sets its own stance toward the content and toward zero findings: for most an empty result is valid; the adversarial lens requires at least ten concrete findings and treats an empty list as a signal to re-check; the editorial lenses hold content sacrosanct and critique only how it is organized and expressed.
The lens set is whatever {workflow.lenses} resolves to, not a fixed list — overrides add lenses and replace shipped ones. Never claim a capability from this file; read the resolved lenses and work from those.
Inputs
- content — what to review: a diff, branch, uncommitted changes, file, spec, story, or any document. Args:
[path]. - lenses (optional) — one or more lens codes or names, however the caller expresses them: a spoken request, or a directive of the form
skill:bmad-review lenses=<code>[,<code>...](the form bmm'sdoc_standardsuses). Default: every applicable lens (a full review). - also_consider (optional) — areas to keep in mind alongside each lens's normal analysis.
- claims (optional) — the change's own narrative: the commit messages it covers, or whatever description of it the caller supplied. Goes to the edge-case lens alone.
- pre-resolved customization (optional) —
[workflow]field values supplied by a forwarding caller. See Execution step 1.
Conventions
- Bare paths (e.g.
references/lens-edge-case-hunter.md) resolve from{skill-root}— this skill's installed directory, wherecustomize.tomllives.{project-root}resolves to the project working directory. {workflow.<name>}resolves to fields incustomize.toml's[workflow]table (overrides win per BMad merge rules).- In
style_guide,review_guidance, andpersistent_facts, a value prefixedfile:is a path or glob — load that file's contents. If afile:value cannot be read, name the failed file in the output header and continue: the shipped baseline forstyle_guide, the remaining entries otherwise.
Execution
- Resolve customization:
uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow. On failure, read{skill-root}/customize.tomldirectly and use defaults. Forwarded activation: if a caller invoked you with pre-resolved customization fields (e.g. thebmad-editorial-reviewshim), honor them verbatim for those named fields — they already carry the user's overrides — and resolve only the remaining fields from your owncustomize.toml. Then execute each{workflow.activation_steps_prepend}entry in order, hold{workflow.persistent_facts}as standing context for the session, and treat{workflow.review_guidance}entries as standing review directives for every lens. - Load the content. Stage it once as a file: when the content is a branch, uncommitted work, or a commit range, use the repository's version-control tooling to write the unified diff to a uniquely-named file in the system temp directory and take that file's absolute path as the content. A branch means its diff against the merge base with its base branch; uncommitted work includes untracked files. Stage
claimsto its own file the same way — it is input for one lens, staged separately precisely so the other lenses never see it. If the content is empty or cannot be decoded as text: when the caller expects the raw findings JSON array (e.g. the legacy edge-case forwarder), return[{"location":"N/A","trigger_condition":"Input empty or undecodable","guard_snippet":"Provide valid content to review","potential_consequence":"Review skipped — no analysis performed"}](nolensfield) and stop; otherwise say what's wrong and ask for reviewable content. Classify the content — diff, source file, function, or document — and whether it is code or docs; scope rules and lens applicability both depend on it. A document that defines behavior (spec, requirements, plan, story) isdocsthat a behavioral lens may still apply to; judge bywhen. - Select lenses from
{workflow.lenses}. A lens with an emptyinstructionis disabled. If the user or caller named lenses, run exactly those only —applies_toandwhendo not filter an explicit request. Otherwise run every enabled lens whoseapplies_tocovers the content class (anyalways covers) and whosewhenapplies. - Announce the plan in one line before running anything: the content class, the lenses about to run, and — when any lens has
afterset — that it runs on top of the named lens's findings. Skip the announcement entirely when the caller pinned an exact output contract (the legacy forwarders that demand raw JSON or one exact line) — their contract covers everything you emit, not just the findings block. Then execute each{workflow.activation_steps_append}entry in order. - Run the independent lenses — every selected lens without
after. Each sees the content andalso_consider, never another lens's findings. Follow each lens'sinstruction; the shipped lenses load their reference file just-in-time, so load only what runs. When subagents are available, launch every independent lens before handling any lens's result. Try running them simultaneously: spawn one per lens; give it the lensinstructionwith{skill-root}and paths resolved absolute, the absolute path of the staged content file (a lens prompt carries the path and the lens reads the file, never the content bytes; inline the content only when it was never staged as a file), anyalso_considerareas, the standing review directives, theclaimspath to the edge-case lens alone (marked to leave unread until its instructions call for it), and the constraint "Return ONLY your findings — no other output. Do not invoke any skill, and do not spawn subagents of your own — you are the reviewer. Return your findings as text in your final message; do not route them through any findings-reporting tool the host may offer." Otherwise run the lenses sequentially yourself, completing one before starting the next. - Run the dependent lenses — every selected lens with
after, once the lens it names has completed, passing that lens's findings in. A lens whoseaftertarget was not selected or produced nothing still runs, with no prior findings. Dependent lenses that name different targets are independent of each other: launch every ready one before handling any of their results. Try running them simultaneously. When subagents are available, spawn them with the same constraint as independent lenses: "Return ONLY your findings — no other output. Do not invoke any skill, and do not spawn subagents of your own — you are the reviewer. Return your findings as text in your final message; do not route them through any findings-reporting tool the host may offer." - Assemble and present per Output below. Keep every lens's findings — overlap between lenses is signal, not duplication; note it in the markdown report rather than deduping. Execute
{workflow.on_complete}if set.
Output
One JSON array holding every finding from every lens. Each finding carries:
lens— the code of the lens that produced itlocation— where in the content (file:line-range for code, section for documents)trigger_condition— the problem, or the condition that exposes it, in one lineguard_snippet— the concrete fix, guard, or missing checkpotential_consequence— what goes wrong if it ships as-is
Each lens file refines these semantics for its findings and may add lens-specific fields (e.g. kind/confidence on deletion findings, gap_shape/consumer/evidence on verification-gap findings). A lens file may instead declare its own findings shape and rendering — the editorial lenses render a findings table — and that shape wins for that lens's findings. [] is valid when nothing is found. No severity, priority, or ranking anywhere.
Present per {workflow.output_format} — "json" (the raw array in a fenced json block), "markdown", or "both" — unless the caller requested a specific shape; a legacy forwarder's output contract always wins, and governs everything you emit rather than the findings block alone. The markdown report groups findings by lens, each rendered in its declared shape: a short block per finding rendering the fields plus any extras worth surfacing, one line for a lens that found nothing, and a plain clean statement when the whole review is clean. Shape the report per {workflow.output_preferences}.
When {workflow.report_path} is set, write the report there; otherwise present it in chat.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

