translation-hunter

Scan TypeScript files to detect and migrate hardcoded Arabic/English strings into i18n translations.

Updated Dec 5, 2025
One-click install
npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill translation-hunter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translation-hunter
Source: https://github.com/ApothecaryMan/pharmaflow-ai/tree/main/.agent/skills/translation-hunter
Command: npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill translation-hunter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the detection and migration of hardcoded Arabic and English strings into a structured internationalization (i18n) system, improving code consistency and language support.

Core Features & Use Cases

  • Ultra-fast Detection: Scans TSX/TS files for hardcoded strings and extracts them.
  • Migration: Inserts detected strings into i18n/translations.ts with English and Arabic translations.
  • Use Case: When working on a multilingual application, this Skill helps ensure all UI strings are properly translated and stored, reducing manual efforts and errors.

Quick Start

Run the 'translation-hunter' skill to scan your codebase for hardcoded strings.

Frequently Asked Questions about translation-hunter

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

FAQPage Schema
How do I detect hardcoded strings in TypeScript files for i18n migration?

Hardcoded string detection scans TypeScript files using regex pattern matching to locate embedded Arabic and English text. The Skill extracts these strings and migrates them into an i18n translations file to maintain a multilingual codebase.

What is the best way to automate extracting Arabic strings into a translation file?

Automating Arabic string extraction involves scanning TypeScript files to find hardcoded text and migrating the detected strings directly into an i18n translations file. This process reduces manual effort and ensures strings are structured for internationalization.

Can I use this string detection approach with my existing i18n translations file?

Yes, this approach integrates with your existing i18n setup by inserting detected Arabic and English strings directly into your translations file. It edits the file to append translations, ensuring your current internationalization structure remains intact.

How does internationalization string detection work for multilingual codebases?

Internationalization string detection works by scanning TypeScript codebases for hardcoded Arabic and English text using regex patterns. Once detected, the strings are extracted from the source code and migrated into a centralized i18n system to support multiple languages.

Does automated i18n migration support both English and Arabic text extraction?

Automated i18n migration supports both English and Arabic text extraction by scanning TypeScript files for hardcoded strings in both languages. It extracts the detected text and inserts it into a translations file with the corresponding English and Arabic entries.

What are the limitations of regex pattern matching for hardcoded string detection?

Regex pattern matching for hardcoded string detection is limited to scanning TypeScript files, meaning it may not capture complex string concatenations or dynamic template literals accurately. It requires a structured i18n directory to migrate the extracted translations successfully.