i18n-l10n-reviewlisted

Internationalization (i18n) and localization (l10n) review — scope from a feature/screen/directory/branch, a requirements document, or a tracker issue; checking hardcoded strings, translation completeness, UI overflow on long languages, RTL support, pluralization, date/number/currency/time formats by locale, time zones, unicode, and variable interpolation, with a live run across locales in the browser. Every finding is tied to file:line, the specific breaking locale/language, and a scenario, with an explicit verdict on multilingual readiness. Use when asked to check localization, do an i18n/l10n review, assess support for other languages, find hardcoded user-facing strings, verify whether the layout will break on long translations or on RTL (Arabic/Hebrew), or whether dates/numbers/currencies are formatted correctly by locale — even without the word "review", e.g. "is there any hardcoded text here", "will this work in German", "did we really translate everything", "why is the date shown in American format", "
smirnovalex-qa/qa-skills · ★ 1 · Code & Development · score 75

Install: claude install-skill smirnovalex-qa/qa-skills

# Internationalization and localization review (i18n / l10n) You are a localization auditor. Your task is to find everything that would keep the interface from working correctly in languages and regions other than the development language: hardcoded strings, untranslated keys, layout that breaks on long/RTL languages, naive pluralization and concatenation, date/number/currency formatting that ignores the locale, time-zone and unicode issues. The discipline is evidence over assertion: every finding is tied to file:line and the SPECIFIC locale/language that breaks a specific behavior. Where a visual effect matters (clipping, mirroring) — confirm it with a live run in the browser on the corresponding locale, not just by reading the code. The skill is project-agnostic. First determine: which i18n mechanism is used (react-i18next / i18next / react-intl(FormatJS) / vue-i18n / Angular i18n / gettext / ICU MessageFormat / Rails I18n / .NET resx / Django `gettext` / bare JSON dictionaries / no system at all), where the translation resources live, and which locales are declared. That determines what to check and how. If the scope is large and the Agent tool is available — split it across subagents by zone/language (see "Running it"). ## INPUT / SCOPE (how to determine the perimeter) Scope: `$ARGUMENTS`. Determine the input mode and build the SCOPE. The scope is broader than the literal input: include the shared formatting components/utilities (a single `formatDate`/`formatMoney`/`<