- Home
- Skills
- Game Development
- Loc Sync — Keep Translations in Sync with Updates
More screenshots
Works with the AI Agents you already use
Loc Sync — Keep Translations in Sync with Updates
Synchronize translations with updated source files using fingerprinting to catch stale and modified strings.
$3
Loc Sync — Keep Translations in Sync with Updates
Example session with this skill installed
The upstream mod just updated to v1.5.0. Compare the new default.json with our v1.4.0 baseline and show me what needs re-translating for the German locale.
- Read your context and instructions
- Compiled the loc sync
I have analyzed the changes between v1.4.0 and the current v1.5.0 source. The update contains 12 new strings and 5 stale strings where the English source text was modified.
Sync Report: v1.5.0 Update
| Key | Status | Source Diff (v1.4.0 -> v1.5.0) | Current Translation (DE) |
|---|---|---|---|
UI_MENU_START | Stale | "Press [START] to play" -> "Press {0} to play" | Drücken Sie [START] zum Spielen |
OPT_GFX_ULTRA | New | N/A (Added key) | [Missing] |
MSG_SAVE_ERR | Stale | "Error saving game" -> "Save failed: Disk full" | Fehler beim Speichern |
NPC_GREET_01 | Removed | Key no longer exists in source | Hallo Reisender |
WP_SWORD_DESC | Stale | "A sharp blade." -> "A rusty blade." | Eine scharfe Klinge. |
Technical Summary
- New Keys: 12 (Requires initial translation)
- Stale Keys: 5 (Source changed, translation is now inaccurate)
- Removed Keys: 3 (Obsolete, will be purged on merge)
- Placeholders: Warning -
UI_MENU_STARTnow requires{0}but the German text is hardcoded.
Next steps
- Run
python3 scripts/locsync.py mergeto remove the 3 obsolete keys. - Run
python3 scripts/loctx.py prepare --keys UI_MENU_START,MSG_SAVE_ERR,WP_SWORD_DESCto update stale translations. - Use
loc-qato verify the new{0}placeholder renders correctly in the German UI.
Connects securely to your tools. The creator never sees your data.
About this skill
Updating a translated app or game mod usually means hunting through thousands of lines for a handful of changed source strings. This skill automates the detection of new, removed, and stale keys by tracking source fingerprints. It prevents the "silent bug" where a source string changes its meaning or placeholders while the old translation remains, leading to inaccurate text or application crashes.
What it does
- Source tracking creates a baseline of source strings to detect future changes accurately.
- Delta reporting generates word-level diffs showing exactly how source text evolved.
- Stale detection flags translations that no longer match the modified source logic.
- Key management identifies and removes obsolete keys while preserving file layout and comments.
- Progress logging tracks translation coverage and history across multiple versions.
How it works
- Establish baseline by running the
baselinecommand against the current state or a specific git revision. - Analyze updates using the
diffcommand to compare the new source against the baseline or old files. - Clean and prep by running
mergeto remove dead keys andtodoto export specific keys for translation. - Finalize update by recording the new state and generating a localized changelog.
Frameworks & tools
The skill operates via a Python CLI (locsync.py) and interacts with .l10n.json files and git repositories. It produces reports in HTML and Markdown formats and integrates with loc-translate and loc-qa workflows.
Why this beats prompting it yourself
Generic LLM prompts miss "stale" translations where the source changed but the key remained. This skill uses precise fingerprinting to ensure 100% of upstream changes are caught, even when placeholders or punctuation updates would otherwise go unnoticed.
Use cases
- Syncing a community game mod translation after a major patch.
- Updating mobile app localizations when source placeholders change.
- Generating a "What's New" changelog for a specific language release.
- Auditing a translation for technical debt and obsolete keys.
Known limitations
Requires a structured .l10n.json format and a local Python environment. It does not perform the actual translation itself, which requires the companion loc-translate skill.
Requires Python 3 environment. Works specifically with .l10n.json formats. Does not perform automated translation, only synchronization and diffing.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 21 days ago