// Compares UniGetUI JSON locale files against English, identifies untranslated or source-changed keys, and generates patch, reference, and handoff files for a target language. Use when the user asks to export missing translations, untranslated strings, i18n diffs, or locale-file changes.
Synchronizes the UniGetUI English language file with source-code usage, identifies missing translation keys, removes unused entries, reports localization drift, and can reorder locale files to match the English key ordering. Use when the user asks to sync language files, missing translations, i18n drift, or align locale file ordering with English.
Analyzes checked-in UniGetUI language files to calculate translation percentages, surface untranslated coverage data, and generate localization status reports.
Merges translated key-value pairs from a UniGetUI JSON localization patch back into the full language file and validates the merged result. Use when the user asks to apply, merge, or import a translation patch.
Translates a sparse UniGetUI JSON language patch, writes completed entries into the working copy, preserves placeholders and terminology, and prepares the patch for merge-back. Use when the user asks to translate or localize i18n strings, localization JSON, or language-file patches.
Reviews UniGetUI .json language files for localization quality, detects parity issues, English-equal entries, wrong-script content, and cross-language outliers, then generates a dataset for LLM-assisted linguistic review. Use when the user asks to review translations, audit localization, inspect i18n or l10n quality, or validate language files.
| name | translation-diff-export |
| description | Compares UniGetUI JSON locale files against English, identifies untranslated or source-changed keys, and generates patch, reference, and handoff files for a target language. Use when the user asks to export missing translations, untranslated strings, i18n diffs, or locale-file changes. |
Use this skill when you need a small UniGetUI translation patch instead of sending a full language JSON file for review or translation.
It exports only the active untranslated or source-changed strings, creates the translator handoff files, and prepares the patch set needed by translation-diff-translate and translation-diff-import.
pwsh).git available on PATH.cirup available on PATH.When source strings changed, run translation-source-sync first so lang_en.json reflects current source usage before exporting downstream translation patches.
scripts/export-translation-diff.ps1: Exports JSON patch artifacts and generates a translation handoff prompt.scripts/test-translation-diff.ps1: Runs a local end-to-end smoke test against the checked-in UniGetUI language files.Use this skill's wrapper scripts first; the downstream translate and import steps are documented in translation-diff-translate and translation-diff-import.
Export untranslated French strings only:
pwsh ./.agents/skills/translation-diff-export/scripts/export-translation-diff.ps1 \
-NeutralJson ./src/Languages/lang_en.json \
-TargetJson ./src/Languages/lang_fr.json \
-Language fr
Export untranslated French strings plus English source values changed since origin/main:
pwsh ./.agents/skills/translation-diff-export/scripts/export-translation-diff.ps1 \
-NeutralJson ./src/Languages/lang_en.json \
-TargetJson ./src/Languages/lang_fr.json \
-Language fr \
-BaseRef origin/main
Optional parameters:
-OutputDir (default: generated/translation-diff-export)-KeepIntermediateRun the built-in smoke test:
pwsh ./.agents/skills/translation-diff-export/scripts/test-translation-diff.ps1
For lang_en.json and language fr, the script generates:
generated/translation-diff-export/lang.diff.fr.source.jsongenerated/translation-diff-export/lang.diff.fr.translated.jsongenerated/translation-diff-export/lang.diff.fr.reference.jsongenerated/translation-diff-export/lang.diff.fr.prompt.mdIf -KeepIntermediate is used, git-baseline snapshots are kept under generated/translation-diff-export/tmp/.
The smoke test writes its temporary artifacts under generated/translation-diff-export-demo/.
After export, confirm the patch is usable before handing it off:
.source.json is not empty unless you expected no work for that language..translated.json is sparse and does not contain copied English placeholders for unfinished keys.-BaseRef and compare the resulting .source.json.After exporting the patch, use the generated .prompt.md file with translation-diff-translate to update the sparse translated working copy.
After translating the patch, merge it back into the full language file with translation-diff-import:
pwsh ./.agents/skills/translation-diff-import/scripts/import-translation-diff.ps1 \
-TranslatedPatch ./generated/translation-diff-export/lang.diff.fr.translated.json \
-SourcePatch ./generated/translation-diff-export/lang.diff.fr.source.json \
-TargetJson ./src/Languages/lang_fr.json \
-NeutralJson ./src/Languages/lang_en.json \
-OutputJson ./src/Languages/lang_fr.merged.json
Keep the .translated.json file sparse. If a key is not translated yet, leave it out instead of copying the English source value into the working copy.