translation-checker

Detects i18n issues in source code including hardcoded strings, broken plural rules, and RTL layout breaks.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill translation-checker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: translation-checker
Source: https://github.com/robotijn/ctoc/tree/main/skills/specialized/translation-checker
Command: npx skills add https://github.com/robotijn/ctoc --skill translation-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about translation-checker

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 before internationalization?▼

Scan your source code for hardcoded user-facing literals to detect hardcoded strings before internationalization. This process identifies unwrapped English text across TypeScript, C#, Java, Python, C/C++, and SQL that should use translation functions.

How does ICU MessageFormat validation work for plural and gender forms?▼

ICU MessageFormat validation checks plural and gender select patterns for CLDR rule compliance across 7 supported languages. It flags missing grammatical categories that cause incorrect output in locales like Russian, Polish, and Arabic.

Can I audit my CSS for RTL layout breaks and bidi injection vulnerabilities?▼

Yes, you can audit CSS for RTL layout breaks by identifying hardcoded directional properties that fail in right-to-left locales. The scan also detects bidi injection vulnerabilities and untranslated accessibility attributes.

What is the best way to find missing translation keys and locale-mismatched date formatting?▼

The best way to find missing translation keys and locale-mismatched date or number formatting is to run a comprehensive source code scan that cross-references locale coverage and generates severity-tiered findings.

Does this i18n checker work for mobile and backend codebases supporting multiple languages?▼

Yes, this i18n checker works for web, mobile, and backend codebases supporting 7 or more languages. It applies to diverse environments and satisfies pre-release localization QA requirements.

What happens when ICU MessageFormat plural validation fails for languages with complex plural rules?▼

When plural validation fails, the checker flags missing grammatical categories required by CLDR rules for complex locales like Russian and Arabic. It generates severity-tiered findings and fix recommendations to correct the broken plural forms.