skills.rest
bketelsen
bketelsenCOMMUNITY
Explore all skills by this author →
Website𝕏@bketelsenGitHub

i18n-validate

Validate i18n JSON files for missing keys, placeholders, and syntax errors.

1|Updated Mar 12, 2026
Search Tags:#quality assurance#validation#localization#translation#i18n#internationalization
One-click install
npx skills add https://github.com/bketelsen/truenas-mcp --skill i18n-validate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n-validate
Source: https://github.com/bketelsen/truenas-mcp/tree/main/.gaai/core/skills/cross/i18n-validate
Command: npx skills add https://github.com/bketelsen/truenas-mcp --skill i18n-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically detects and reports issues in translation files, preventing errors like missing keys, inconsistent phrasing, and formatting mistakes from reaching production.

Core Features & Use Cases

  • Completeness Check: Verifies that every translatable string in the reference language exists in all target languages.
  • Consistency Validation: Ensures placeholders and glossary terms are used correctly across all locales.
  • Quality Assurance: Catches syntax errors, length violations, and potential untranslated strings.
  • Use Case: Before merging a new feature with international support, run this skill to guarantee all new UI strings are correctly translated and formatted for French, German, and Spanish users.

Quick Start

Validate all translation files in the 'locales/' directory for English, French, German, and Spanish languages, using English as the reference.

Frequently Asked Questions about i18n-validate

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

FAQPage Schema
How do I validate i18n JSON files for missing translation keys?▼

You validate i18n JSON files by comparing a reference language against target locales to detect missing keys, orphaned keys, and placeholder mismatches. This ensures translation completeness and consistency across all specified languages.

What causes placeholder mismatches in localization files?▼

Placeholder mismatches in localization files happen when dynamic variables in target languages do not align with the reference language. Validation checks detect these inconsistencies, ensuring formatting placeholders are correctly used across all locale JSON files.

How do I check translation JSON files for length violations and glossary terms?▼

To check translation JSON files, apply configurable length budgets and glossary rules to localized strings. This quality assurance step identifies length violations, glossary deviations, and potential untranslated strings across target languages.

Does internationalization validation catch JSON syntax errors?▼

Yes, internationalization validation catches JSON syntax errors during the completeness check. It parses specified locale paths to identify syntax issues, preventing broken formatting mistakes from reaching production across multiple languages.

Can I use a reference language for key validation across multiple target locales?▼

Yes, you can use a reference language for key validation by operating on specified locale paths and languages. The validation ensures every translatable string in the reference exists in all target languages, verifying completeness and consistency.

Related Skills

Explore More Software Engineering Skills→
Fr-e-dFr-e-d
157

i18n-validate

Validate i18n JSON files for missing translations, placeholder mismatches, and syntax errors.

Community
Advanced
FAIQahmFAIQahm

translation-sync

Synchronize English MDX files with Urdu translations for Docusaurus i18n.

Community
Advanced
petrkohutpetrkohut

bmad-testarch-test-review

Automate test quality review and validation against best practices.

Community
Advanced
mikopbxmikopbx
569

restapi-translations

Synchronize missing and unused REST API translation keys in PHP projects.

Official
Intermediate