i18n-maintenance

Validate translation JSON files and detect missing, extra, or orphaned keys across locales.

1|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill i18n-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-maintenance
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/i18n-maintenance
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill i18n-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps translation JSON files and code-based translation calls in sync to prevent missing keys, orphaned translations, and inconsistent placeholders across locales, using en-US as the source of truth.

Core Features & Use Cases

  • Structure validation: Compare en-US key paths with other locale files to detect missing or extra keys.
  • Code↔JSON verification: Scan code for useTranslations and t() calls and confirm referenced keys exist in the locale JSON.
  • Unused key discovery: Identify translation keys present in JSON but never referenced in code to find legacy or removable entries.
  • Value consistency checks: Validate placeholders and embedded HTML/markdown are consistent across locales.
  • Use case: Before release, run a full sweep to ensure new components' translation keys are added to en-US and propagated as placeholders to other locales.

Quick Start

Use the i18n-maintenance skill to validate translation coverage, find missing or unused keys, and sync the en-US structure to other locales.

Frequently Asked Questions about i18n-maintenance

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

FAQPage Schema
How do I detect missing translation keys in my locale JSON files?

To detect missing translation keys, validate your locale JSON files against the en-US reference to find missing, extra, or orphaned key paths. This structure validation ensures all locales maintain consistent translation coverage across your project.

How do I find unused i18n translation keys in TypeScript TSX code?

Find unused i18n translation keys by scanning your TypeScript/TSX code for useTranslations and t() calls to identify JSON entries that are never referenced. This discovers legacy or removable translation keys present in your locale files.

How do I verify code and JSON parity for translation placeholders in i18n projects?

Verify code↔JSON parity by scanning t() calls to confirm referenced keys exist in the locale JSON and checking that placeholders and embedded HTML markup are consistent across all locales. This prevents MISSING_MESSAGE errors during runtime.

What is the best way to sync en-US translation structure to other locales before release?

The best way to sync locale structures is to run a full validation sweep ensuring new components' translation keys are added to en-US and propagated as placeholders to other locales. This enforces en-US as the source of truth for translation completeness.

Does this translation validation work with useTranslations and t() patterns in TSX?

Yes, this translation validation specifically supports projects using useTranslations and t() patterns in TypeScript/TSX code. It scans these exact patterns to verify that referenced translation keys exist within your locale JSON files.