skills.rest
btabaska
btabaskaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Update Translations

Scan React/JSX codebases for missing i18n keys and generate locale patches.

1|1|Updated Mar 31, 2026
Search Tags:#frontend#react#diff#i18n#translations#patch#locales
One-click install
npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill update-translations
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Update Translations
Source: https://github.com/btabaska/simpler-grants-documentation-automation/tree/main/.cursor/skills/skill-update-translations
Command: npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill update-translations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping i18n keys in sync across locales can be error-prone and time-consuming.

Core Features & Use Cases

  • Detect missing locale keys by comparing English keys against translations in other locales.
  • Generate patches with TODO_TRANSLATE placeholders for non-English locales.
  • Emit a diff for review without writing files, enabling safe patch review.

Quick Start

Run the tool to scan your frontend code for i18n keys and produce a patch that brings all locales in sync.

Frequently Asked Questions about Update Translations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect missing i18n translation keys across multiple locale JSON files?▼

You can detect missing i18n keys by scanning your React project to compare English translation keys against other locale JSON files. The tool identifies keys referenced via t('...') that are absent in non-English locales.

How do I generate a patch for missing translations without overwriting my locale files?▼

To generate a patch for missing translations, the tool scans your frontend code and produces a diff with TODO_TRANSLATE placeholders for non-English locales. It emits this diff for review without writing to your files.

Does this tool work with any React internationalization library or only specific i18n setups?▼

This tool works specifically with React/JSX projects using the frontend/src/i18n/messages/<locale>/*.json directory structure. It detects translation keys referenced via t('...') or similar patterns in your codebase.

What is the best way to keep i18n keys in sync across locales during frontend development?▼

The best way to keep i18n keys in sync is to scan your frontend codebase to detect missing keys and generate patches with TODO_TRANSLATE placeholders. This produces a diff for review without modifying your files.

Can I automatically fill in missing translation keys with placeholder text for non-English locales?▼

Yes, you can automatically fill missing translation keys with placeholder text. The tool generates patches that insert TODO_TRANSLATE placeholders into non-English locales for any missing keys detected during the scan.

Why are my non-English locale JSON files missing translation keys that exist in English?▼

Non-English locale JSON files miss translation keys when new t('...') references are added to the codebase without updating other locales. This tool detects these discrepancies by comparing English keys against other locales.

Related Skills

Explore More Software Engineering Skills→
allenlin90allenlin90
1

frontend-i18n

Implement type-safe frontend i18n workflows with Paraglide and @eridu/i18n.

Community
Intermediate
virajpvirajp
1

internationalization

Organize Flutter localization with ARB files and l10n.yaml workflows.

Community
Intermediate
parisgroup-aiparisgroup-ai
1

i18n-maintenance

Validate translation JSON files and detect missing, extra, or orphaned keys across locales.

Official
Intermediate
mateo19182mateo19182

i18n

Automate React i18n tasks by extracting hardcoded strings and replacing them with translation keys.

Community
Intermediate