check-l10n

Check L10n Skill

Purpose

Catch the two ways localization breaks in this repo before users see English in a non-English build:

1. Untranslated keys. A key added to app_en.arb but never translated into one of the 21 non-English locales (am, ar, bg, de, es, fil, fr, id, it, ja, ko, ms, nl, pl, pt, ro, sv, tr, ur, vi, zh). mobile/lib/l10n/app_*.arb is the live list.
2. Hardcoded user-visible English. Strings rendered straight to the user from widget code without going through context.l10n.<key>. These never show up in .arb files because they were never extracted, so no amount of translation work fixes them.

Run this before every PR push that touches mobile/lib/.

This skill checks that a string is translated. Whether it is translated in the locale's voice is a separate question with its own source of truth: mobile/docs/LOCALIZATION_STYLE_GUIDE.md carries the per-locale register table, the Spanish dialect decision, the terms that never get translated, and the review tiers.

Workflow

Step 1: Determine scope

If the user passed paths after /check-l10n, scan those. Otherwise scan the union of staged + unstaged changes vs the working tree.

# Default: changed files
git -C mobile status --porcelain | awk '{print $NF}' | grep '\.dart$'

# Or explicit: argument paths

Step 2: Run the arb consistency test (if present)

cd mobile && flutter test test/l10n/arb_consistency_test.dart

This test compares every .arb file against app_en.arb and fails if any locale is missing keys that aren't on the explicit _knownUntranslatedDebt allow-list.

If the test file does not exist on this branch, skip this step and rely entirely on Step 3 plus the inline check below. Note in the report that arb consistency was not verified.

Inline fallback when the test doesn't exist

If mobile/test/l10n/arb_consistency_test.dart is missing, do the equivalent check by hand: