i18n-gap-check

Name: i18n-gap-check
Availability: InStock
Author: AlphaBitCore

Detect missing translations and hardcoded strings in frontend locale files.

21|3|Updated May 26, 2026

Search Tags:#automation #localization #i18n #translations #gap-analysis #i18n-gap #ui-locales

Ready to run

npx skills add https://github.com/AlphaBitCore/nexus-gateway --skill i18n-gap-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n-gap-check
Source: https://github.com/AlphaBitCore/nexus-gateway/tree/main/.claude/skills/i18n-gap-check
Command: npx skills add https://github.com/AlphaBitCore/nexus-gateway --skill i18n-gap-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans the Control Plane UI and Agent UI locale sources to identify untranslated keys, missing translations, orphaned locale entries, and hardcoded strings that bypass localization, enabling teams to achieve consistent multilingual UI experiences.

Core Features & Use Cases

Scans the two frontend bundles (control-plane-ui and agent-ui) and their shared locale sources to detect: missing EN keys, translation gaps in ES/ZH, orphan translations, and hardcoded strings.
Generates a Markdown gap report with a per-bundle summary and detailed item lists, to guide remediation.
Provides a repeatable workflow to fix Section 1 (missing EN keys) and Section 6 (hardcoded strings), then re-run the gap check to verify improvements.

Quick Start

Run the i18n gap check against your repo to generate a report.

Frequently Asked Questions about i18n-gap-check

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

FAQPage Schema

How do I detect missing translations across UI locale bundles?▼

To detect missing translations across UI locale bundles, scan your frontend locale sources to identify untranslated keys, translation gaps in ES and ZH, and orphaned entries. This generates a Markdown gap report detailing mismatches for guided remediation.

What is an i18n gap analysis for frontend applications?▼

An i18n gap analysis for frontend applications scans locale sources to surface missing EN keys, untranslated ES/ZH strings, orphan translations, and hardcoded strings bypassing localization, ensuring a consistent multilingual UI experience across bundles.

How do I find hardcoded English strings bypassing localization in my codebase?▼

To find hardcoded English strings bypassing localization, run an i18n gap check against your repository's locale directories. The analysis scans frontend bundles and shared locale files to surface hardcoded strings in a Markdown report.

Do I need a specific script to check for orphan keys in my locale files?▼

Yes, you need the i18n_gap_check.py script and access to your repository's locale directories. It analyzes the shared locale files and frontend bundles to surface orphan translations and missing keys across EN, ES, and ZH locales.

What's the best way to fix i18n translation gaps after identifying them?▼

The best way to fix i18n translation gaps is to follow the generated Markdown report's per-bundle summary, remediate missing EN keys and hardcoded strings, then re-run the gap check to verify improvements and confirm no mismatches remain.