translate-docs

Translate and synchronize bilingual Chinese-English documentation pages and changelogs.

6|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Wyl-cmd/kxns-cli --skill translate-docs-wyl-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translate-docs
Source: https://github.com/Wyl-cmd/kxns-cli/tree/main/.agents/skills/translate-docs
Command: npx skills add https://github.com/Wyl-cmd/kxns-cli --skill translate-docs-wyl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining bilingual documentation is error-prone: pages drift out of sync when one language is updated but the other is not. This Skill guides page-by-page, paragraph-by-paragraph translation so Chinese and English docs stay consistent. ## Core Features & Use Cases - Direction-aware translation: Changelogs are translated from English to Chinese, while all other pages are translated from Chinese to English. - Code-grounded accuracy: Consults source code files when needed to ensure technical terms are translated correctly. - Style consistency: Preserves structure and formatting while respecting language-specific conventions such as sentence case and translation glossaries. - Use Case: After updating the Chinese user guide for a CLI tool, run this Skill to produce the matching English pages and keep the changelog bilingual. ## Quick Start Translate the docs directory page by page, keeping the Chinese and English versions in sync following the translation direction rules.

Frequently Asked Questions about translate-docs

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

FAQPage Schema
How do I keep Chinese and English documentation in sync?

Translate page by page and paragraph by paragraph, following a fixed direction per content type. In this workflow, changelogs go from English to Chinese and all other pages go from Chinese to English, ensuring both versions stay aligned.

Which translation direction should changelogs and docs follow?

Changelogs are treated as English-first and translated into Chinese. All other documentation pages are Chinese-first and translated into English, matching the project's established source-of-truth convention.

How do I translate technical terms accurately in documentation?

Refer to the actual source code files when a term is ambiguous, since code reveals the precise meaning of commands, flags, and features. This prevents mistranslations that pure prose context might cause.

Should translated docs keep the same formatting and style?

Yes, structure and markup should stay consistent across languages, but each language keeps its own conventions. For example, English pages may use sentence case and specific translation pairings that differ from Chinese typographic habits.