i18n-localization

Audit codebases for hardcoded strings and missing translation keys.

132|22|Updated Dec 18, 2025

Search Tags:#localization #i18n #translations #rtl #code-audit #locale-files #key-parity

Ready to run

npx skills add https://github.com/xenitV1/Antigravity-Workflows --skill i18n-localization

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/i18n-localization
Command: npx skills add https://github.com/xenitV1/Antigravity-Workflows --skill i18n-localization

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps teams identify hardcoded strings and missing translations, enabling consistent internationalization across applications.

Core Features & Use Cases

Detect hardcoded strings in code bases across JavaScript, Python, and other languages.
Validate locale files and key parity to ensure all languages have the same translation keys.
RTL support checks and general i18n best-practice audits for multi-language projects.
Use Case: A web app with en-US and fr-FR locales can run a quick audit to surface missing keys and replace them with translation keys.

Quick Start

Run the i18n_checker.py script in the project root to generate a locale and code quality report, then review and fix any flagged issues.

Frequently Asked Questions about i18n-localization

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

FAQPage Schema

How do I detect hardcoded strings in my codebase?▼

Detecting hardcoded strings involves scanning your code for text values that should be externalized to translation files. Run the i18n_checker.py script in your project root to automatically identify hardcoded strings across JavaScript, Python, and other languages, then review the generated report to replace them with translation keys.

How do I validate that all my locale files have matching translation keys?▼

Key parity validation ensures every language file contains the same set of translation keys. The i18n_checker.py script compares your locale files and flags missing or orphaned keys, so you can synchronize translations across en-US, fr-FR, and other locales before deployment.

Can I audit my React or Vue app for internationalization issues?▼

Yes, i18n audits work across React, Vue, and Python stacks. The Python-based scanner detects hardcoded strings, validates locale file structure, and checks RTL considerations specific to your framework, generating a comprehensive code quality report.

What does RTL support checking accomplish in i18n audits?▼

RTL (right-to-left) support checking identifies code patterns that may break layouts in languages like Arabic and Hebrew. The audit flags alignment assumptions and text-direction handling to ensure your app renders correctly across all locales.

Do I need existing locale files to run an i18n audit?▼

Yes, the audit requires local locale files to verify key parity and translation coverage. The script compares your codebase against these files to surface missing translations and inconsistencies before you deploy multi-language support.