bmad-os-editorial-review-translation

Detect unauthorized additions, omissions, and meaning drift in translated documentation.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-os-editorial-review-translation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-os-editorial-review-translation
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-os-editorial-review-translation
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-os-editorial-review-translation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It verifies that translated documentation stays faithful to the English source and catches injected, off-topic, or missing content before it is published.

Core Features & Use Cases

  • Translation Fidelity Review: Compares headings, section order, links, assets, frontmatter, and code blocks against the source.
  • Injection Detection: Flags unauthorized additions such as promotions, unrelated commentary, new agendas, or external URLs.
  • Use Case: Review a localized docs pull request and quickly identify any drift, omissions, or suspicious material that needs human attention.

Quick Start

Review the translated files against their English source and report any injections, omissions, link mismatches, or meaning drift.

Frequently Asked Questions about bmad-os-editorial-review-translation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect translation drift in localized documentation pull requests?

Translation drift in localized documentation is detected by comparing source-to-target files across headings, links, images, frontmatter, and code blocks, then back-translating suspicious passages to verify fidelity.

What is the best way to review translated docs for unauthorized injected content?

Reviewing translated docs for injected content requires structural matching against English sources to flag unauthorized additions like promotions, unrelated commentary, new agendas, or external URLs before publishing.

How do I check bilingual documentation for missing sections and link mismatches?

Checking bilingual documentation for omissions and link mismatches involves performing file pairing against English sources, verifying structural matching, and conducting link inventory checks to ensure target files match the source.

Can I automate back-translation for suspicious passages in localized docs review?

Back-translation for suspicious passages is applied during localized docs review to verify meaning fidelity when structural matching identifies potential drift, omissions, or injections requiring human attention.

What causes translation drift in documentation localization workflows?

Translation drift in documentation localization workflows is caused by unauthorized additions, omissions, and meaning shifts that occur when target files deviate from the English source structure, links, assets, and code blocks.