agentleFS
s977043s977043/river-review/skills/midstream/i18n-unused-key/SKILL.md

i18n Unused Key Review

Skill7 starsChanged 5 months agoMITView on GitHub

Detect i18n/locale keys that are removed from source but remain in locale files, or keys added to locale files without source usage.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check if translation keys deleted from source code (e.g., t('key'), i18n.t('key'), $t('key')) still exist in locale JSON files — report as …

    line 37
  2. Distinctive:

    Check if new keys added to locale JSON files are referenced in source code — report as potentially orphaned key.

    line 38
  3. Very specific:

    Look for patterns like t('user.profile.name'), i18n('common.cancel'), formatMessage({ id: 'key' }).

    line 39
  4. Distinctive:

    When source file is deleted entirely, flag all its keys in locale files as candidates for removal.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Pattern declaration

Primary pattern: Reviewer Secondary patterns: Inversion Why: i18n key管理はdiff単体では判断が難しく、ファイル全体とソース参照の両方を踏まえる必要がある

Guidance

  • Check if translation keys deleted from source code (e.g., t('key'), i18n.t('key'), $t('key')) still exist in locale JSON files — report as unused key.
  • Check if new keys added to locale JSON files are referenced in source code — report as potentially orphaned key.
  • Look for patterns like t('user.profile.name'), i18n('common.cancel'), formatMessage({ id: 'key' }).
  • When source file is deleted entirely, flag all its keys in locale files as candidates for removal.

Non-goals

  • 動的に構築されるkey(テンプレートリテラルやconcat)は誤検知になりやすいため指摘しない。
  • 外部ライブラリのkey(third-party component内部のi18n keyなど)は対象外。

Pre-execution Gate / 実行前ゲート

このスキルは以下の条件がすべて満たされない限りNO_REVIEWを返す。

  • 差分にi18n/locale関連ファイル(*.json, /i18n/, /locales/)の変更が含まれている
  • または差分にUI文言を削除・変更するソースコードの変更が含まれている

ゲート不成立時の出力: NO_REVIEW: i18n-unused-key — i18n/locale関連の変更が検出されない

False-positive guards

  • keyがワイルドカードや動的参照で使用されている可能性がある場合は黙る。
  • テスト用フィクスチャやstorybook内のkey定義は対象外。
  • 同一PR内で追加と削除が対になっている(リネーム)場合は指摘しない。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.