i18n-validate

Name: i18n-validate
Availability: InStock
Author: petrsimonidesxart

Validate multilingual locale files for missing translations and glossary mismatches.

Updated Mar 8, 2026

Search Tags:#validation #glossary #i18n #translations #ci #locales

Ready to run

npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill i18n-validate-petrsimonidesxart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n-validate
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/cross/i18n-validate
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill i18n-validate-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate translation completeness across multiple locales, detect missing keys, orphaned entries, and glossary mismatches to ensure UI text quality before deployment.

Core Features & Use Cases

Missing translations detection across locales
Placeholder consistency, length budgets, and glossary alignment
CI/CD and PR validation workflows for i18n assets

Quick Start

Run the i18n-validate skill against your locales to generate a validation report.

Frequently Asked Questions about i18n-validate

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

FAQPage Schema

How do I check for missing translations across multiple locale files before deployment?▼

To check for missing translations across multilingual locale files, validate your locale assets to identify gaps, orphaned keys, and placeholder inconsistencies. This generates a structured JSON report with a per-language completion breakdown and actionable recommendations for pre-release QA.

Can I validate i18n glossary mismatches and placeholder consistency in a CI pipeline?▼

You can validate i18n glossary mismatches and placeholder consistency within CI workflows by running pre-merge checks on your locale files. This enforces JSON syntax validity, glossary alignment, and length budgets, producing structured output suitable for blocking invalid pull requests.

What is the best way to detect orphaned keys in multilingual JSON locale files?▼

Detecting orphaned keys in multilingual JSON locale files involves scanning your locale directories to find entries present in some languages but missing in others. This process highlights unused or incomplete translations across specified locales like en, fr, de, and es.

Does i18n validation enforce length budgets and JSON syntax validity for translation assets?▼

i18n validation enforces length budgets and JSON syntax validity by checking translation assets against defined constraints before release. It identifies syntax errors and over-limit strings across your locales, ensuring UI text quality and preventing layout breaks in deployed applications.

How do I get a per-language completion breakdown for my translation files?▼

To get a per-language completion breakdown for your translation files, run a validation check across your locale assets. This produces a structured JSON output detailing the completion percentage and specific gaps for each language, giving you actionable pre-release recommendations.

What are the limitations of automated translation validation for pre-release QA?▼

Automated translation validation for pre-release QA focuses on structural completeness, syntax validity, and glossary alignment, but does not assess linguistic quality, cultural nuance, or contextual flow of the translated text across your supported locales.