skills.rest
mikecubed
mikecubedCOMMUNITY
Explore all skills by this author →
GitHub

i18n-check

Detect hardcoded strings, locale-unaware formatting, and missing translation keys in TypeScript, JavaScript, and Python codebases.

Updated Mar 18, 2026
Search Tags:#typescript#python#javascript#localization#translation#i18n#code-analysis
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill i18n-check-mikecubed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n-check
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/ccc/skills/i18n-check
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill i18n-check-mikecubed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internationalization enforcement to prevent hardcoded user-facing strings, locale-unaware formatting, and missing translation keys across TypeScript, JavaScript, and Python projects.

Core Features & Use Cases

  • Detect hardcoded user-facing strings and enforce translation routing.
  • Flag locale-unaware date/number formatting and recommend locale-aware alternatives.
  • Validate translation keys against the default locale file and surface actionable fixes.

Quick Start

Run the i18n check against your codebase to identify hardcoded strings, locale formatting issues, and missing translation keys.

Frequently Asked Questions about i18n-check

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

FAQPage Schema
How do I detect hardcoded user-facing strings in my codebase?▼

To detect hardcoded user-facing strings, you can run a static analysis check against your source files to flag any unlocalized text and enforce translation routing across UI components and API responses.

What is internationalization enforcement and why do I need it?▼

Internationalization enforcement prevents i18n defects by identifying hardcoded strings, locale-unaware formatting, and missing translation keys, ensuring your application is fully translatable across global markets.

How do I validate missing translation keys against my default locale file?▼

You can validate missing translation keys by inspecting your locale files during code reviews, surfacing actionable fixes to update translation keys and synchronize them with your default locale configuration.

Does i18n static analysis work with both TypeScript and Python projects?▼

Yes, i18n static analysis works with TypeScript, JavaScript, and Python projects, allowing you to audit source files, inspect locale configurations, and apply actionable guidance across these languages.

How do I fix locale-unaware date and number formatting in my application?▼

To fix locale-unaware date and number formatting, you can use static analysis to flag non-compliant formatting and recommend locale-aware alternatives for your date and number rendering logic.

Can I integrate i18n checks into my CI processes?▼

Yes, you can integrate i18n checks into your CI processes to audit code continuously, catching hardcoded strings and missing translation keys automatically before deployment.

Related Skills

Explore More Software Engineering Skills→
CrazyDubyaCrazyDubya

internationalization-helper

Extract hardcoded strings and manage translation files across locales.

Community
Intermediate
cute-baobaocute-baobao

i18n

Manage react-i18next translation keys and locale data for React applications.

Community
Intermediate
buihuulocbuihuuloc

ue-localization-scanner

Scan Unreal Engine C++ and Blueprint codebases for hardcoded strings and localization issues.

Community
Advanced
KaakatiKaakati
2

i18n

Implement internationalization and localization for Rails, React Native, ReactJS, and Next.js applications.

Community
Advanced