AGENT SKILL

translate

Fill untranslated strings in the shared web and mobile translation catalogs (`packages/i18n/locales/*/messages.po`) and open or update the translation pull request. Use when asked to translate the app, fill translation gaps, or update the "Update translation catalogs" pull request, and on the scheduled translation run.

License 许可
Apache-2.0
所属仓库
elie222/rakazo
最近更新
2026-11-15
Stars
★ 8.4k
Forks
1.5k

01 前言 Front Matter

name
translate
description
Fill untranslated strings in the shared web and mobile translation catalogs (`packages/i18n/locales/*/messages.po`) and open or update the translation pull request. Use when asked to translate the app, fill translation gaps, or update the "Update translation catalogs" pull request, and on the scheduled translation run.

02 资源文件 2

03 SKILL.md 正文

Translate the catalogs

catalog-gaps.ts, next to this file, finds and fills empty entries without touching anything else. Run it from the repo root.

1. Pick the branch

If an open pull request from i18n/catalog-sync exists (gh pr list --head i18n/catalog-sync --state open), check out that branch; otherwise branch i18n/translate-<date> from origin/main. Either way, bring in the newest strings before translating:

  1. Merge origin/main. If a messages.po conflicts, keep the branch's copy (git checkout --ours -- <file>) so its translations survive, and finish the merge.
  2. Run pnpm intl:extract. It adds main's new strings and drops removed ones, keeping every existing translation.
  3. Fill in anything main translated that the branch had not, for each locale: git show origin/main:packages/i18n/locales/<locale>/messages.po > /tmp/main-<locale>.po, then node .agents/skills/translate/catalog-gaps.ts apply <locale> /tmp/main-<locale>.po.
  4. Commit the result.

Run node .agents/skills/translate/catalog-gaps.ts check. If it exits 0, push what step 1 committed if you are on i18n/catalog-sync (your own branch needs no pull request when nothing changed), and stop. Otherwise translate the gaps and fix any reported mismatch.

2. Translate

For each locale with gaps, node .agents/skills/translate/catalog-gaps.ts list <locale> prints the empty entries with their source files and placeholder notes. With several locales, fan out one subagent per locale (pair the small ones).

  • Read the catalog's existing translations first and match their terms, tone and formality. Keep "Rakazo" and other names as they are.
  • Keep every placeholder ({name}, {0}), numbered tag (<0>…</0>, <1/>) and plural #. In plural/select messages keep the structure and variable, translate only the branch text, and use the language's own plural categories (Russian one/few/many/other, Hebrew one/two/other, Japanese, Korean and Chinese only other).
  • Short labels stay short. Read the source file when the meaning is unclear. Use the source text for code, URLs and example values.

Write translations as JSON objects { "<key>": "<translation>" }, about 120 per file, using the exact key from list. Apply each file with node .agents/skills/translate/catalog-gaps.ts apply <locale> <file.json>; it only fills entries that are still empty.

3. Verify

  • node .agents/skills/translate/catalog-gaps.ts check exits 0.
  • pnpm exec lingui compile --strict passes.
  • pnpm exec vitest run apps/web/src/lib/i18n apps/web/src/lib/agent-import-locales apps/web/src/lib/bot-templates-locales apps/mobile/lib/i18n passes.
  • Only translations changed: git diff -U0 -- packages/i18n/locales | grep -E '^[-+][^-+]' | grep -vE '^[-+]msgstr ' prints nothing.

4. Ship

Commit only the messages.po files and push. On i18n/catalog-sync, that push starts CI and stops the sync workflow from overwriting the branch until it merges. On your own branch, open a pull request titled "Translate new strings" that says which locales changed and that no native speaker reviewed them.

Take it to green with .agents/skills/pr-watch/SKILL.md. If you were asked to merge, squash-merge once checks pass and review comments are resolved.

04 同仓库更多 Skills

elie222
elie222/rakazo

search-docs

Search the connected documentation server. Use when the user asks how a documented feature works or wants a source for an answer.

★ 8.4k
elie222
elie222/rakazo

say-hello

Greet the user by name and suggest one thing to try next. Use when the user says hello or asks what you can do.

★ 8.4k
elie222
elie222/rakazo

ux-declutter

Review a screen for visual noise and redesign it to be calm — fewer elements, one accent, progressive disclosure, the main action first. Use whenever you build or change UI on web, desktop or mobile, before calling it done, and whenever you look at a screenshot of your own UI.

★ 8.4k
elie222
elie222/rakazo

release

Prepare a Rakazo release - draft the CHANGELOG section from the pull requests merged since the last tag, bump the desktop version, open the release PR, and tag it once merged. Use when asked to cut, prepare, or ship a release or a new version.

★ 8.4k
elie222
elie222/rakazo

pr-watch

Take an open pull request to green — wait for CI, triage failing checks, and answer review-bot comments — using one backgrounded observation per cycle. Use when monitoring or babysitting a PR, waiting on checks or review bots, or addressing PR review feedback.

★ 8.4k
elie222
elie222/rakazo

composio

Route and complete Composio work across Composio For You and Composio Platform. Use when the user mentions Composio; wants an agent to use apps such as Gmail, Slack, GitHub, Notion, Calendar, or Linear; needs first-time setup, an SDK or MCP integration, CLI operation, migration guidance, current documentation, or help diagnosing a connection or tool call.

★ 8.4k