i18n-localization

Detect hardcoded strings and verify i18n locale keys in React, Vue, and Python projects.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/lchenrique/politron-ide --skill i18n-localization-lchenrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/lchenrique/politron-ide/tree/main/.agent/skills/i18n-localization
Command: npx skills add https://github.com/lchenrique/politron-ide --skill i18n-localization-lchenrique

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps teams detect and fix hardcoded strings, ensuring codebases are ready for localization and internationalization across languages.

Core Features & Use Cases

  • Detect hardcoded text in React, Vue, and Python projects.
  • Verify i18n usage patterns (t, useTranslation, $t, gettext) and ensure translation keys exist in locale files.
  • Provide quick-start guidance and recommended checks during code reviews or CI.

Quick Start

Run the i18n_checker.py script against your project to identify hardcoded strings and locale gaps.

Frequently Asked Questions about i18n-localization

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

FAQPage Schema
How do I find hardcoded strings in React and Vue projects?

To find hardcoded strings in React and Vue projects, run the i18n checker script to scan project files, detect untranslated text, and verify usage of translation APIs like t and $t.

What is the best way to enforce i18n readiness during code reviews?

The best way to enforce i18n readiness during code reviews is to scan for hardcoded strings and verify that all text uses translation APIs, ensuring locale keys exist across language files before merging.

Does this i18n checker work with Python gettext localization?

Yes, the i18n checker works with Python projects by verifying gettext usage patterns and scanning files to ensure all strings are properly translated and locale keys exist in language files.

How do I verify that translation keys exist in locale files?

To verify translation keys exist in locale files, the i18n checker scans your project and locale directories, flagging any untranslated text or missing keys across your language files.

Can I integrate hardcoded string detection into CI pipelines?

Yes, you can integrate hardcoded string detection into CI pipelines by running the i18n checker script to enforce i18n readiness, ensuring all strings use translation APIs and locale keys are validated.