skills.rest
junnv93
junnv93COMMUNITY
Explore all skills by this author →
GitHub

verify-i18n

Validate en/ko translation key parity and route-map synchronization.

Updated Aug 23, 2026
Search Tags:#validation#localization#translation#navigation#i18n#route-metadata
One-click install
npx skills add https://github.com/junnv93/equipment_management_system --skill verify-i18n
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-i18n
Source: https://github.com/junnv93/equipment_management_system/tree/main/.claude/skills/verify-i18n
Command: npx skills add https://github.com/junnv93/equipment_management_system --skill verify-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies i18n translation consistency across English and Korean assets, ensuring every key exists in both languages, translations are not empty, and routes and labels stay in sync.

Core Features & Use Cases

  • Validate en/ko key parity across all translation files.
  • Detect empty translations and warn about missing values.
  • Verify namespace references used by useTranslations/getTranslations align with available keys.
  • Check ICU placeholder consistency across languages.
  • Detect dynamic i18n keys and ensure all enum values have corresponding translations.
  • Cross-check routeMap with navigation.json and route definitions.

Quick Start

After modifying apps/frontend/messages/en/ko/*.json or route-metadata.ts, run the verification to confirm all keys, values, and mappings are consistent.

Frequently Asked Questions about verify-i18n

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

FAQPage Schema
How do I validate en/ko translation key parity in my frontend project?▼

To validate en/ko translation key parity, check every key exists in both English and Korean translation files under apps/frontend/messages. This ensures consistent internationalization behavior by detecting missing keys and empty translations.

What is the best way to verify namespace references for useTranslations in i18n?▼

Verifying namespace references for useTranslations involves checking that the namespaces align with available keys in your translation files. This ensures dynamic keys and enum values have corresponding translations to prevent missing text.

How do I cross-check routeMap with navigation.json and route-metadata.ts?▼

Cross-checking routeMap with navigation.json and route-metadata.ts involves verifying route-map synchronization between route definitions and navigation labels. This keeps routes and labels in sync across English and Korean translations.

Can I detect empty translations and missing ICU placeholders across en/ko files?▼

You can detect empty translations and missing ICU placeholders by auditing translation consistency across English and Korean assets. This checks ICU placeholder symmetry across languages and warns about missing values.

Does this i18n validation require any external dependencies to run?▼

This i18n validation requires no external dependencies to run. It directly audits translation files under apps/frontend/messages and related navigation metadata to enforce English and Korean key parity.

Related Skills

Explore More Software Engineering Skills→
btabaskabtabaska
1

Update Translations

Scan React/JSX codebases for missing i18n keys and generate locale patches.

Community
Intermediate
gagan114662gagan114662

github

Manage GitHub repositories, pull requests, issues, and Actions workflows via gh CLI and APIs.

Community
Intermediate
mauriciodelriomauriciodelrio
3

i18n-nextjs-rules

Configure next-intl internationalization for Next.js App Router projects.

Community
Intermediate
TimeKastTimeKast

i18n-localization

Detect hardcoded strings and missing translation keys in locale JSON files.

Official
Intermediate