translation-review

Reviews UniGetUI JSON language files for parity, wrong-script, and untranslated entries.

25.9k|915|Updated Jun 15, 2021
One-click install
npx skills add https://github.com/Devolutions/UniGetUI --skill translation-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translation-review
Source: https://github.com/Devolutions/UniGetUI/tree/main/.agents/skills/translation-review
Command: npx skills add https://github.com/Devolutions/UniGetUI --skill translation-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually auditing large localization JSON files for mistranslations, untranslated strings, and placeholder mismatches is slow and error-prone. This Skill mechanically flags quality issues in UniGetUI language files and builds a cross-language comparison dataset so an agent can perform the final linguistic review.

Core Features & Use Cases

  • Parity Detection: Flags placeholder, HTML-fragment, and newline mismatches between the English source and the translated value.
  • English-Equal and Wrong-Script Detection: Finds entries still equal to English in non-English files and entries missing the expected script (Cyrillic, CJK, Arabic, Hebrew, and more) for non-Latin languages.
  • Cross-Language Comparison Table: Generates a Markdown or JSON report comparing the target translation against all other checked-in language files to surface outliers and wrong-language content.
  • Use Case: Run the review script against lang_fr.json, read the flagged sections of the generated report, spot-check the comparison table, and report each confirmed issue with a suggested correction.

Quick Start

Review the French translation file for quality issues and generate a report of flagged entries with cross-language comparisons.

Frequently Asked Questions about translation-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a UniGetUI translation file for quality issues?

Run the review-translation-json.ps1 script with the target language JSON and language code, for example lang_fr.json with -Language fr. It writes a Markdown report to generated/translation-review with parity issues, English-equal entries, wrong-script entries, and a cross-language comparison table.

How do I detect untranslated strings in a JSON language file?

The script flags entries whose translated value exactly equals the English source in a non-English file, excluding technical tokens like URLs, numbers, and short identifiers. These appear in the English-Equal Entries section of the report for manual confirmation.

Does the translation review support non-Latin scripts like Arabic or Chinese?

Yes, the script checks expected Unicode script ranges for languages including ar, he, ja, ko, ru, ua, zh_CN, and zh_TW. Entries lacking the expected script are flagged in the Wrong Script section, which is almost always a genuine error.

What do I need to run the translation review script?

You need PowerShell 7 (pwsh) and the UniGetUI repository checked out, since the script loads shared helpers from scripts/translation and reads language files from src/Languages. No external modules are required.

Why is the cross-language comparison table empty in my report?

The table is omitted when you pass the -FlaggedOnly switch, which emits only mechanically flagged entries. Remove that switch to include the full comparison table built from the other checked-in lang_*.json files.