agentleFS
MysterionRiseMysterionRise/forgetest/.agents/skills/bmad-editorial-review/SKILL.md

bmad-editorial-review

Skill4 starsChanged 33 days agoMITView on GitHub

Deprecated — forwards to bmad-review.

5 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use bmad-eval-runner, bmad-module-builder and 2 more.

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.
  • bmad-code-orgSkill

    bmad-eval-runner

    Run a skill's evals and report results. Use when the user wants to evaluate a skill, run evals, benchmark a skill, validate triggers, optimize a description, or grade skill outputs.

    Also in 3 projects that use this

  • bmad-code-orgSkill

    bmad-module-builder

    Plans, creates, and validates BMad modules. Use when the user requests to 'ideate module', 'plan a module', 'create module', 'build a module', or 'validate module'.

    Also in 3 projects that use this

  • laraxotSkill

    bmad-agent-builder

    Builds, edit or validate Agent Skill through conversational discovery. Use when the user requests to "Create an Agent", "Optimize an Agent" or "Edit an Agent".

    Also in 3 projects that use this

  • laraxotSkill

    bmad-workflow-builder

    Builds workflows and skills through conversational discovery and validates existing ones. Use when the user requests to "build a workflow", "modify a workflow", "quality check workflow", or "optimize skill".

    Also in 3 projects that use this

The file

Files
SKILL.md

Merged into bmad-review. Invoke the bmad-review skill on the same content with the structure and prose lenses — both, structure first, so prose runs on top of the structure findings — unless the caller asked for a structure-only or prose-only review, in which case pass only that lens. Pass through any also_consider areas, and forward this skill's resolved [workflow] fields as pre-resolved values — but only those that resolved to something, since an empty value here means no legacy override exists and bmad-review's own default should stand: reader_type, style_guide, review_guidance, output_preferences, persistent_facts, activation_steps_prepend, activation_steps_append, on_complete, and review_output_path as the report path. Present the findings in the legacy shape: the two-pass findings table | Pass | Original Text | Revised Text | Changes | with the purpose/audience read above it and, when the structure pass ran, the reduction summary below it — and no other lens's output.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.