ada-bilingual-doc-audit

Audits bilingual documentation pairs for fact drift, broken commands, and fake translations.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-bilingual-doc-audit-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-bilingual-doc-audit
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-bilingual-doc-audit
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-bilingual-doc-audit-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Translated documentation pairs (English canonical plus Chinese mirror) silently drift apart: commands get corrupted, version numbers diverge, tables lose rows, and sometimes the translation is never actually written. This Skill performs a rigorous read-only audit that proves whether two language versions of the same document still tell the same facts. ## Core Features & Use Cases - Fact and command integrity checks: Verifies that untranslatable tokens (versions, commands, env vars, identifiers) exist in both languages and that code blocks are byte-identical across the pair. - Migration and manifest audits: Validates git mv rename history (R100), recomputes manifest blob triplets with git hash-object, and checks status-table consistency for phase-scoped documentation migrations. - Contract-pair semantic audits: Compares SRS/HLD/ADR pairs on requirement tuples, modal strength (must/should/may), traceability matrices, and supersession links, plus fake-translation detection via CJK character counts. - Use Case: After a repo switches to an English-canonical README with a synchronized Chinese translation, run this audit to confirm every install command survived translation byte-for-byte, all links resolve, and the repo's own validators still pass, without modifying a single file. ## Quick Start Ask the agent to audit the bilingual README pair in this repository for fact drift and broken commands, producing a severity-ranked findings report.

Frequently Asked Questions about ada-bilingual-doc-audit

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

FAQPage Schema
How do I audit a bilingual README pair for consistency?

Freeze the repo state with git status, then verify every untranslatable token (versions, commands, paths) exists in both files, byte-compare all code blocks, and check that language-switch links resolve both ways. Finish by re-running the repo's own validators and confirming git status is unchanged.

How to detect a fake translation that was never actually translated?

Count CJK characters in the Chinese file with a Python regex rather than grep. A header-only count (for example 28 characters all inside the language bar) proves the body is byte-identical English and the translation was never produced, even when tests and validators pass.

Does this audit modify files or commit changes?

No, the audit is strictly read-only. It freezes git status before and after all checks, sets PYTHONDONTWRITEBYTECODE to avoid __pycache__ pollution, and the identical final status is cited in the report as proof nothing was created, modified, committed, or pushed.

Can it verify git mv migrations preserved file history?

Yes, it runs git diff --cached --name-status -M and requires every move to report R100, proving history preservation. It also recomputes manifest blob triplets with git hash-object and git ls-files -s instead of trusting the manifest's declared values.

When should I not use the bilingual doc audit?

Skip it for single-language document edits, doc-to-code consistency checks (use ada-doc-implementation-audit), or merging two drafts (use ada-doc-comparison-analysis). It targets translation-pair verification, not general document review.