← ClaudeAtlas

github-repo-i18nlisted

Internationalize the user-facing language layer of a GitHub repository, including its repository description, repository topics, README files, release notes, changelogs, and other explicitly selected documentation, with English as the default and any user-requested locales as mirrors. Use when a user asks to translate, localize, add language mirrors, or check cross-locale parity for a GitHub repository. Confirm the exact document and metadata scope when it is not explicit, identify existing locales, preserve facts, code, commands, links, images, and structure, and provide local Markdown plus GitHub-style previews. Do not use for product UI or runtime i18n, database content, visual README redesign or assets, public-release suitability or security scans, Issue or PR label taxonomies, Git tags, or Git, PR, release, deployment, or production operations.
WardLu/skills · ★ 1 · Code & Development · score 67
Install: claude install-skill WardLu/skills
# GitHub Repository Internationalization Synchronize the selected language layer of a GitHub repository while keeping every locale faithful to the same project facts. Treat repository description and repository topics as separate metadata surfaces, and treat each documentation locale as a complete mirror rather than a shortened translation. ## Scope gate Before editing, identify the exact documentation categories, files, metadata surfaces, and target locales. If the request does not name the documentation scope, ask: > Which parts should be internationalized: repository description, repository topics, README files, release notes, CHANGELOG, docs pages, documentation indexes, templates, or specific files? Which locales should be added or updated? Everything else will remain unchanged. Treat repository description and repository topics as independent choices. Do not infer that a request for a README includes GitHub metadata, or that a metadata request includes documentation. A short read-only inventory is allowed before the scope answer when it helps present the choices. Do not write, rename, delete, or remotely update anything until the scope is explicit. Preserve unrelated working-tree changes and never switch or overwrite another worktree. ## Workflow ### 1. Inventory the selected repository Read the applicable repository instructions, then inspect only enough of the repository to establish the confirmed scope: - Check the current worktree, branch, other worktrees