roo-translation

Translate Roo Code extension and WebView UI strings across multiple locales.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/cheafi/Trading-bot-CC --skill roo-translation-cheafi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roo-translation
Source: https://github.com/cheafi/Trading-bot-CC/tree/main/.roo/skills/roo-translation
Command: npx skills add https://github.com/cheafi/Trading-bot-CC --skill roo-translation-cheafi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roo Code localization work is error-prone and time-consuming, especially when keeping placeholders, namespaces, and UI patterns consistent across many languages.

Core Features & Use Cases

  • Guides consistent i18n updates for both the VSCode extension backend (src/i18n/locales/) and the WebView UI (webview-ui/src/i18n/locales/), including when to change only user-facing strings.
  • Preserves technical correctness by maintaining exact interpolation placeholders like {{variable}} and keeping i18next React patterns (including Trans with named components) intact.
  • Provides a safe translation workflow that prioritizes updating English first, using targeted diffs (apply_diff) for existing files, and validating completeness with the missing-translations script.

Quick Start

Update the English entries in the appropriate locale files, then use apply_diff to propagate the changes to all supported languages and run the missing translations validation script.

Frequently Asked Questions about roo-translation

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

FAQPage Schema
How do I add new i18n translation keys for the WebView UI and VSCode extension?

To add new i18n translation keys, update the English locale files in both `src/i18n/locales/` and `webview-ui/src/i18n/locales/` first, then apply targeted diffs to propagate changes to all supported languages.

How do I fix broken interpolation placeholders in React i18next components?

To fix broken interpolation placeholders in React i18next, preserve the exact placeholder syntax like `{{variable}}` and maintain named component patterns within the `Trans` block while updating localized strings across all locale files.

What is the best workflow for updating existing localization strings without breaking UI patterns?

The best localization workflow involves updating English entries first, using targeted `apply_diff` edits for existing locale files to avoid overwriting context, and validating completeness with the missing-translations validation script.

Does the translation workflow require updating English locale files first before other languages?

Yes, the translation workflow requires updating English locale files first to establish the baseline. After updating English entries, you propagate the changes to all supported languages using targeted diffs to ensure structural consistency.

How do I validate missing translations across multiple locales in a VSCode extension?

You validate missing translations by running the missing-translations validation script after updating locale files. This script checks completeness across both the VSCode extension backend and WebView UI directories to identify any unlocalized strings.

Why are my interpolation variables disappearing when I update i18n locale files?

Interpolation variables disappear when translations do not preserve exact placeholder syntax like `{{variable}}`. To fix this, ensure your translation workflow maintains strict technical correctness by keeping all React i18next interpolation variables intact during string updates.