agentleFS
lifedeverlifedever/skills-plugin/skills/localize/SKILL.md

localize

Skill14 starsChanged 6 months agoMITView on GitHub

Batch update multi-language localization files in parallel. Use when user says: "更新多语言", "本地化更新", "翻译到所有语言", "update all languages", "localize", "多语言同步", or asks to apply a change across multiple language files.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use soak-test, team-live-ops and 10 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.
  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 9 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 9 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the baseline language file (usually Chinese or English) to understand the change:

    line 29
  2. Distinctive:

    Remove the deleted keys

    line 41
  3. Distinctive:

    After every agent finishes:

    line 48
  4. Distinctive:

    If the project has lint / build commands, run them

    line 50
  5. Distinctive:

    Wait for user confirmation before committing

    line 51
  6. Distinctive:

    Don't assume the language file format — read it first to confirm

    line 55
  7. Distinctive:

    If one language file's format differs from the others, handle it individually rather than templating across the board

    line 57

“Common” is measured: kept by at least 6 in 10 of the 23 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

Localize — Batch Multi-Language Update

Propagate a single content change across every language file in the project, using parallel agents to speed things up.

Workflow

1. Identify Language Files

Scan the project for localization files. Common patterns:

  • locales/*.json / locales/*.yml
  • i18n/*.ts / i18n/*.js
  • lang/*.php
  • *.lproj/*.strings (macOS / iOS)
  • Or a path the user specifies

List every language file found and ask the user to confirm.

2. Understand the Change

Read the baseline language file (usually Chinese or English) to understand the change:

  • Added keys and copy
  • Modified copy
  • Removed keys

Show the user a change summary and continue after confirmation.

3. Update All Languages in Parallel

Spawn one agent per language file, running concurrently. Each agent must:

  • Preserve the existing structure and unchanged translations of that language file
  • Translate the changed content (new / modified copy)
  • Remove the deleted keys
  • For new content that can't be translated accurately, fall back to the baseline copy with a comment marker

Important: each agent must verify that the file's original structure is fully preserved — no unchanged content can be lost.

4. Recap and Confirm

After every agent finishes:

  1. Show a change summary table (number of edits per language)
  2. If the project has lint / build commands, run them
  3. Wait for user confirmation before committing

Notes

  • Don't assume the language file format — read it first to confirm
  • Preserve each file's original key ordering
  • If one language file's format differs from the others, handle it individually rather than templating across the board

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.