agentleFS
elie222elie222/rakazo/.agents/skills/translate/SKILL.md

translate

Skill8.6k starsChanged 2 days agoApache-2.0View on GitHub

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.

48 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about elie222/rakazo

The biggest 5 of 86 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 86

Talked about on GitHub, YouTube, the web and Bluesky (86 times).

On GitHub · 50

45 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 6

1 more on Bluesky

Used with

Projects with it also use faq, summarize and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    faq

    Turn repeat questions into a pinned FAQ. Use when a champion keeps answering the same questions.

    Also in 3 projects that use this

  • mitsuhikoSkill

    summarize

    Fetch a URL or convert a local file (PDF/DOCX/HTML/etc.) into Markdown using `uvx markitdown`, optionally it can summarize

    Also in 8 projects that use this

  • jacobraskSkill

    calendar

    Interact with Apple Calendar via AppleScript. Use when the user asks to check calendar, view events, create events, manage schedule, find free time, or list calendars. Triggers include "my calendar", "my schedule", "calendar events", "create event", "add to calendar", "what's on my calendar", "free time", "available slots", "upcoming events", "today's events". Requires macOS with Calendar.app.

    Also in 3 projects that use this

  • AnthropicSkill

    analyze

    Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

    Also in 4 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 5 projects that use this

  • MicrosoftSkill

    web-search

    Also in 3 projects that use this

  • +2 more from anthropics

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 0 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If an open pull request from i18n/catalog-sync exists (gh pr list --head i18n/catalog-sync --state open), check out that branch.

    line 12
  2. Very specific:

    Run pnpm intl:extract. It adds main's new strings and drops removed ones, keeping every existing translation.

    line 15
  3. Very specific:

    Run node .agents/skills/translate/catalog-gaps.ts check.

    line 19
  4. Very specific:

    Read the catalog's existing translations first and match their terms, tone and formality.

    line 25
  5. Very specific:

    Write translations as JSON objects { "<key>": "<translation>" }, about 120 per file, using the exact key from list.

    line 29
  6. Very specific:

    Only translations changed: git diff -U0 -- packages/i18n/locales | grep -E '^[-+][^-+]' | grep -vE '^[-+]msgstr ' prints nothing.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.