translation-checker

What problem does it solve?

Shipping code with hidden internationalization bugs creates broken experiences for non-English users, including untranslated strings, grammatically incorrect plural/gender forms, broken RTL layouts, and missing translation keys that often only surface after launch when fixes are costly and reputation-damaging.

Core Features & Use Cases

• Hardcoded string detection: Scans code for user-facing English literals that should be wrapped in i18n translation functions across TypeScript, C#, Java, Python, C/C++, SQL, and other common languages.
• ICU MessageFormat validation: Checks plural and gender select patterns for compliance with CLDR rules for 7 supported languages, flagging missing categories that cause grammatically incorrect output for locales like Russian, Polish, and Arabic.
• RTL and formatting audits: Identifies hardcoded directional CSS that breaks right-to-left locales, locale-mismatched date/number/currency formatting, untranslated accessibility attributes, and bidi injection vulnerabilities.
• Use case: For a team launching a SaaS product in 10 locales, run this skill during code review to catch all i18n issues before they reach production, avoiding post-launch fixes and user frustration.

Quick Start

Use the translation-checker skill to scan your project's codebase for all internationalization and localization bugs before your next release.