CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmad-review

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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, well-sequenced orchestration skill: every step carries concrete commands, fallbacks, and verbatim prompts, with error-recovery loops at each fragile point and reference content correctly pushed to just-in-time lens files. The main costs are a duplicated subagent-constraint quote between steps 5 and 6, labyrinthine nested sentences in steps 2 and 5, and no explicit listing of the shipped lens reference files.

Suggestions

In step 6, drop the full re-quote of the subagent constraint after "the same constraint as independent lenses:" — the reference back is sufficient and saves ~50 tokens.

Split the mega-sentences in steps 2 and 5 (e.g. the staging and empty-input rules) into short bullet sub-steps; the parenthetical nesting obscures otherwise clear rules.

Add a one-line list of the shipped lens reference files (or a note that customize.toml's lens entries name their instruction files) so the bundle's structure is discoverable from SKILL.md itself.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ("Report what is real — never pad to look thorough"), with no explanation of known concepts. However, step 6 re-quotes the full subagent constraint that step 5 already establishes, and steps 2 and 5 are heavily nested parenthetical sentences that could be split, keeping it below anchor 5.

4 / 5

Actionability

Fully executable guidance: the exact resolve_customization.py invocation, a copy-paste-ready fallback JSON array for empty/undecodable input, verbatim subagent prompt text, and precise decision rules (branch = diff against merge base, untracked files included, claims staged separately). This matches the instruction-only analogue of copy-paste-ready code.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit error-recovery feedback loops at every fragile point: script-not-found → offer setup; other failure → read customize.toml directly; empty input → exact JSON response and stop; dependent lenses wait on `after` targets with defined behavior when the target produced nothing. Operations are read-only staging, so no destructive-validation cap applies.

5 / 5

Progressive Disclosure

SKILL.md is an orchestrating overview with lens details correctly split into references/ and explicit just-in-time loading ("load only what runs"), over a flat bundle. Minor gaps: the body never enumerates the shipped lens reference files for discoverability (naming one only as a path-convention example), and lens-prose/lens-structure chain a second hop to editorial-common.md / structure-models.md — a shared-common pattern rather than buried content, so this stays at anchor 4 rather than 3 or 5.

4 / 5

Total

18

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it names the full lens set concretely, answers both what and when with an unusually explicit trigger and exclusion policy, and stays concise in third person. Its two soft spots are missing natural synonyms for the review trigger and residual overlap risk with generic code-review skills; note also that "triaged findings" slightly over-claims, since the body's canonical output explicitly has no severity, priority, or ranking.

Suggestions

Add the natural synonyms users actually say for the trigger — "PR", "critique", "look over my changes" — alongside "diff" and "pull request".

Replace "reports triaged findings" with a phrase matching the actual output (e.g. "reports findings in a canonical shape, unranked") to avoid over-claiming.

Name the differentiator from a plain code review (running the installed BMad lens set) within the first sentence to further reduce confusion with generic review skills.

DimensionReasoningScore

Specificity

"Runs one or more installed review lenses — adversarial critique, edge cases, verification gaps, structure, prose — and reports triaged findings" lists multiple concrete actions with comprehensive coverage of the skill's lens set, matching the anchor-5 example pattern.

5 / 5

Completeness

Both halves are explicit: the what ("Runs one or more installed review lenses — ... — and reports triaged findings") and the when with concrete trigger phrases and exclusions ("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'").

5 / 5

Trigger Term Quality

Good natural-phrase coverage: "review a diff", "a pull request", "artifact", "code or documents", "act on feedback", and the literal trigger "actually says 'review'". A few natural synonyms (PR, critique, look over) are missing, so it sits at anchor 4 rather than the comprehensive-synonym anchor 5.

4 / 5

Distinctiveness Conflict Risk

Strong boundary carving ("an explicit skill:bmad-review directive from another skill counts"; "a change, not a review"; "Never invoke this uninvited") gives it distinct triggers, but the core trigger — reviewing a diff or PR — is exactly the trigger space of generic code-review skills, leaving minor overlap risk with closely related skills rather than anchor 5's minimal risk.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

bmad-code-org/BMAD-METHOD

Path

skills/bmad-review/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.