skills.rest
onemanking
onemankingCOMMUNITY
Explore all skills by this author →
GitHub

localize

Extract, validate, and report localization strings and translation coverage for source code.

Updated Apr 13, 2026
Search Tags:#localization#i18n#internationalization#string extraction#coverage report#translation validation
One-click install
npx skills add https://github.com/onemanking/the-operator --skill localize-onemanking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/localize
Command: npx skills add https://github.com/onemanking/the-operator --skill localize-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It detects hardcoded user-facing strings, missing translations, and placeholder mismatches so a codebase stays ready for multi-locale releases without manual audits. ## Core Features & Use Cases - Scan for Issues: Find hardcoded strings, positional placeholders, non-locale-aware date/number formatting, and left-to-right assumptions in src/. - Extract and Update String Tables: Generate new key entries following the [category].[subcategory].[description] convention and output diffs against string tables in assets/data/. - Validate and Report Status: Check translations for missing entries, placeholder mismatches, length violations, and orphaned keys, then produce a per-locale coverage matrix. - Use Case: Before shipping a new game update, run the validate subcommand to confirm every locale has complete translations and no UI strings exceed their character limits. ## Quick Start Ask the assistant to run the localize skill with the status subcommand to generate a localization coverage report for the project.

Frequently Asked Questions about localize

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

FAQPage Schema
How do I find hardcoded strings in my source code before localization?▼

Run the scan subcommand to search src/ for string literals not wrapped in a localization function, concatenated strings, and positional placeholders like %s. Findings are reported with file paths and line numbers.

How to extract new translatable strings into a string table?▼

Use the extract subcommand to scan source files for localized string references and compare them against existing tables in assets/data/. It generates new entries with keys following the category.subcategory.description convention and outputs a diff for review.

How do I validate translations for missing keys and placeholder mismatches?▼

Run the validate subcommand to check every string table entry for missing translations, placeholder mismatches such as a missing {name}, character limit violations, and orphaned keys. Results are grouped by locale and severity.

Does the localization workflow support right-to-left languages?▼

Yes, RTL support is treated as a design requirement from the start. The scan subcommand flags strings that assume left-to-right text direction so layouts can be adapted before adding RTL locales.

Can the skill edit translation files directly?▼

No, translation files are never modified directly. The workflow generates diffs of proposed changes for human review, and every string table entry must include a translator comment explaining context.

Related Skills

Explore More Software Engineering Skills→
tranhieutttranhieutt
70

localize

Scan source files for hardcoded strings and localization anti-patterns.

Community
Advanced
sumilee-pcusumilee-pcu

localize

Manage game localization lifecycle from string extraction to VO pipeline integration.

Community
Advanced
AlexDevFlowAlexDevFlow

test-responsive

Run automated responsive tests across four viewports with Playwright.

Community
Intermediate
polsegupolsegu

localize

Automate game localization pipelines from string extraction to QA reports.

Community
Advanced