What problem does it solve?
Maintaining four parallel README files (Korean, English, Japanese, Chinese) in a repository leads to drift: sections fall out of order, translations diverge, and shared elements like the language-switcher header get broken. This Skill defines the exact procedure to keep all four files structurally identical.
Core Features & Use Cases
- Canonical-first workflow: Author changes in README.ko.md (the primary source), then derive en, ja, and zh versions with minimal diffs in the same PR.
- Hard contracts and parity checklist: Enforces the shared language-switcher header, identical H2 section counts and order, matching table rows and code blocks, and a URL blacklist check via grep commands.
- Manual verification recipe: Since no linter exists for READMEs, it provides concrete grep-based checks plus rendering sanity rules (e.g., Mermaid diagrams must use TD/TB direction only).
- Use Case: A maintainer updates the installation section of an open-source project's README. Following this Skill, they edit README.ko.md first, translate only the changed section into the three derived files, then run the parity checklist before merging.
Quick Start
Update the Korean README.ko.md with your change, derive the English, Japanese, and Chinese files, then run the section-order parity checklist to verify all four files match.
