bmad-os-editorial-review-translation

Audit translated documentation against English source files for fidelity.

8|2|Updated Feb 1, 2026

Search Tags:#quality assurance #documentation #audit #localization #translation #fidelity

Ready to run

npx skills add https://github.com/bmad-code-org/bmad-utility-skills --skill bmad-os-editorial-review-translation-bmad-code-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-os-editorial-review-translation
Source: https://github.com/bmad-code-org/bmad-utility-skills/tree/main/skills/bmad-os-editorial-review-translation
Command: npx skills add https://github.com/bmad-code-org/bmad-utility-skills --skill bmad-os-editorial-review-translation-bmad-code-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the introduction of unauthorized content, hidden agendas, or meaning drift in translated documentation by rigorously comparing it against the original English source.

Core Features & Use Cases

Fidelity Auditing: Automatically detects injected messaging, off-topic additions, or unauthorized links in translated files.
Structural Comparison: Validates that headings, links, and frontmatter remain consistent between source and target languages.
Use Case: Use this when reviewing a pull request for a new language localization to ensure the translation is faithful to the original English documentation and free of external agendas.

Quick Start

Run the bmad-os-editorial-review-translation skill on the current pull request to compare the translated files against the English source directory.

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 unauthorized content injections in translated documentation?▼

To detect content injections in translated documentation, perform a structural and semantic fidelity audit comparing target files against the English source. This process identifies off-topic additions, hidden messaging, and unauthorized links introduced during localization.

What is translation fidelity auditing and how does back-translation work?▼

Translation fidelity auditing verifies that localized content maintains the original intent and structure of the source material. It utilizes back-translation and structural mapping to compare translated files against English sources, detecting meaning drift and omissions.

How do I validate structural consistency between English source files and localized translations?▼

Validating structural consistency involves mapping translated documentation against English source files to ensure headings, frontmatter, and links remain intact. This structural comparison catches unauthorized modifications and formatting drift in localization workflows.

Can I use this to review a pull request for a new language localization?▼

Yes, you can review a pull request for a new language localization by running an editorial audit on the translated files. It compares the changes against the original English documentation directory to ensure faithfulness and prevent external agendas.

What is the best way to prevent meaning drift in documentation localization workflows?▼

The best way to prevent meaning drift in localization workflows is to perform a semantic fidelity audit using back-translation. This rigorously compares translated documentation against the original English source to verify integrity and identify unauthorized content.

Why do translated files sometimes contain off-topic additions or unauthorized links?▼

Translated files contain off-topic additions or unauthorized links when external agendas are introduced during localization. Running a structural and semantic fidelity audit detects these injected messages by verifying translated content against the original English source material.