comet-bilingual-docs

Synchronizes Chinese and English documentation, READMEs, Skills, and release notes for Comet.

2.9k|284|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-bilingual-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-bilingual-docs
Source: https://github.com/rpamis/comet/tree/main/assets/skills-maintainer/comet-bilingual-docs
Command: npx skills add https://github.com/rpamis/comet --skill comet-bilingual-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping Chinese and English documentation in sync is error-prone: translations drift, terminology changes silently, and website pages diverge from repository docs. This Skill enforces a disciplined bilingual documentation workflow for the Comet repository so both language versions preserve confirmed semantics, structure, and terminology.

Core Features & Use Cases

  • Semantic-first synchronization: Confirms authoritative Chinese wording before translating, and pauses for user confirmation on Skill content before producing the English version.
  • Scoped, careful edits: Preserves examples, command names, config keys, links, anchors, and code fences, and treats the website docs directory as an independent repository with its own commit flow.
  • Validation and reporting: Runs Prettier, git diff --check, mint validate for website changes, and focused repository contract tests, then reports source language, synced file scope, and deferred translations.
  • Use Case: After updating the Chinese README and Changelog for a Comet release, use this Skill to produce the matching English versions and website pages while keeping terminology and information architecture consistent.

Quick Start

Use the comet-bilingual-docs skill to synchronize the updated Chinese README and Changelog into their English counterparts and validate the changes.

Frequently Asked Questions about comet-bilingual-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?

Confirm the authoritative Chinese wording first, then translate into English without changing confirmed user-visible terms. This Skill enforces that order, preserves code samples and links, and validates results with Prettier and git diff checks.

How to translate technical documentation without changing terminology?

Lock down accepted terms before translating and never silently alter confirmed wording. For example, the workflow term "gate" must not be translated literally; natural Chinese phrasing is used while keeping command names, config keys, and anchors intact.

Does this Skill commit or push documentation changes automatically?

No. It does not commit or push unless the user explicitly requests delivery, in which case it uses the comet-safe-delivery workflow. Website changes are committed in the separate website repository before updating the parent repository gitlink.

What validation runs after bilingual documentation changes?

It runs Prettier and git diff --check on affected files. Website changes are validated with mint validate --disable-openapi from the website repository, and README or contract changes trigger focused repository contract tests when available.

When should translation of Skill content be paused for review?

When Skill content requires user confirmation, the Chinese version is completed first and the English translation is deferred until the user approves. The final report lists any intentionally postponed translations.