extract-i18n-keys

To extract hardcoded strings for i18n from TypeScript and JSX files, run this Skill on specific file paths or directory locations. It identifies user-facing text nodes and automatically replaces them with translation function calls or Trans components.

Automating internationalization key generation is best handled by scanning your codebase for hardcoded text and converting it into semantic, module-prefixed i18n keys based on file location, eliminating manual translation setup.

Yes, this i18n extraction tool supports processing files via git commit hashes. You can input specific commit hashes to target and extract newly added hardcoded strings from your latest code changes for internationalization.

When extracting text from routes versus components, the Skill generates smart i18n keys with appropriate semantic prefixes based on the file location, ensuring organized and context-aware translation keys across your internationalization setup.

No, you cannot run the internationalization extraction process with unstaged git changes. The Skill enforces strict pre-checks for unstaged changes to prevent accidental file overwrites and maintain codebase integrity during extraction.

To replace plain text with translation functions in TSX files, the Skill parses your code to identify string literals and substitutes them with t() or i18n.t() calls, utilizing Trans components specifically for rich text formatting.