What problem does it solve? When English canonical files in a repository change, their maintained Japanese reference translations can silently drift out of sync, or receive unnecessary no-op edits that create review churn. This Skill decides, per maintained file pair, whether a Japanese translation must be created, updated, or explicitly left unchanged. ## Core Features & Use Cases - Pair-scoped maintenance: Covers defined pairs such as README.md → README.ja.md, AGENTS.md → AGENTS-ja.md, docs/<name>.md → docs/ja/<name>.md, and SKILL.md → SKILL-ja.md for English-canonical Skills. - Semantic-impact judgment: Distinguishes meaning-bearing changes (requirements, scope, exceptions, permissions, procedures, links) from non-semantic edits like whitespace reflow, avoiding no-op translation churn. - Fidelity and terminology preservation: Retains normative force (must/should/may), frontmatter fields, headings, links, code, and established repository terminology without adding content absent from the canonical source. - Use Case: After editing an English SKILL.md to strengthen a requirement from 'should' to 'must', run this Skill to update the corresponding SKILL-ja.md while leaving unrelated translations untouched and reporting the semantic reason. ## Quick Start Review the current diff and create or update the maintained Japanese reference translations for any changed English canonical files, reporting which pairs were updated or left unchanged and why.
