translate-docs

Translate and synchronize bilingual Kimi Code CLI documentation in the docs directory.

12|2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/haomingz/kimi-skills --skill translate-docs-haomingz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translate-docs
Source: https://github.com/haomingz/kimi-skills/tree/main/skills/translate-docs
Command: npx skills add https://github.com/haomingz/kimi-skills --skill translate-docs-haomingz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate and synchronize bilingual project documentation for the Kimi Code CLI, ensuring Chinese and English versions stay aligned.

Core Features & Use Cases

  • Translate pages in the docs directory to English and Chinese versions, maintaining parity across languages.
  • Preserve project documentation formatting and terminology while updating changelogs in the target language.
  • Use as part of a documentation localization workflow to accelerate bilingual release notes.

Quick Start

Translate the docs in docs/ to the target bilingual versions with a consistent tone and terminology.

Frequently Asked Questions about translate-docs

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

FAQPage Schema
How do I translate project documentation to maintain bilingual parity?

Translating bilingual project documentation requires consistent terminology and formatting, which this Skill handles by operating on the docs directory page-by-page to ensure Chinese and English versions stay aligned.

How does bilingual documentation synchronization handle changelog updates?

Bilingual documentation synchronization handles changelog updates by applying English-to-Chinese translations, preserving the original formatting and project terminology to maintain accurate bilingual release notes.

Can I use this to translate docs while preserving project terminology and formatting?

Yes, you can translate docs while preserving project terminology and formatting, as the Skill ensures consistent tone and can reference code comments or design notes to verify translation accuracy across pages.

What is the best way to automate bilingual release notes for a CLI project?

The best way to automate bilingual release notes is to integrate this Skill into your documentation localization workflow, translating docs directory pages and changelogs to accelerate the bilingual release process.

Does this documentation localization approach require manual reference to code comments?

Documentation localization does not require manual reference to code comments, as the Skill automatically references code comments and design notes occasionally to ensure translation accuracy and consistent terminology.