verify-i18n-replacements

Validate i18n replacements in changed files against extract-i18n-keys rules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/OrderlyNetwork/dex-creator --skill verify-i18n-replacements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-i18n-replacements
Source: https://github.com/OrderlyNetwork/dex-creator/tree/main/.cursor/skills/verify-i18n-replacements
Command: npx skills add https://github.com/OrderlyNetwork/dex-creator --skill verify-i18n-replacements

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all internationalization (i18n) keys and their translations in the codebase are correctly implemented, adhere to established rules, and avoid common pitfalls like over-extraction.

Core Features & Use Cases

  • Key Validation: Verifies that i18n keys exist in their respective modules and have correct English copy.
  • Rule Compliance: Checks for correct usage of t vs. i18n.t, proper prefixing based on file location, and correct use of the Trans component for rich text.
  • Over-extraction Detection: Identifies content that should not have been internationalized (e.g., URLs, class names, technical strings).
  • Use Case: After a developer implements new UI text and its translations, this Skill can be run on a commit to automatically audit the changes, ensuring all i18n keys are valid, correctly formatted, and that no non-translatable strings were accidentally extracted.

Quick Start

Verify all i18n replacements in the current commit.

Frequently Asked Questions about verify-i18n-replacements

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

FAQPage Schema
How do I validate i18n keys in a commit before merging?

Validate i18n keys in a commit by scoping verification to changed files, checking for missing keys, rule violations, content consistency, and over-extraction of non-translatable strings to produce a structured report.

What is the best way to check for missing translation keys in source code?

Check for missing translation keys by validating replacements against extract-i18n-keys rules and module content, ensuring all internationalization keys exist and have the correct English copy.

How do I prevent over-extraction of non-translatable strings during localization?

Prevent over-extraction of non-translatable strings by running a validation check that identifies URLs, class names, and technical strings that should not have been internationalized.

Can I verify i18n rule compliance for t vs i18n.t usage automatically?

Verify i18n rule compliance automatically by checking for correct usage of t vs i18n.t, proper prefixing based on file location, and correct use of the Trans component for rich text.

Does i18n replacement validation work on specific commit ranges?

I18n replacement validation works by scoping verification to changed files within a given commit or range, operating read-only to produce a structured report without modifying the source code.

When should I run internationalization validation on my codebase?

Run internationalization validation after a developer implements new UI text and translations to automatically audit changes, ensuring all i18n keys are valid, correctly formatted, and no non-translatable strings were accidentally extracted.