localize

Extracts and validates translation strings from source files into diff-ready tables.

33|8|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/TraftG/opencode-game-studio --skill localize-traftg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/TraftG/opencode-game-studio/tree/main/.opencode/skills/localize
Command: npx skills add https://github.com/TraftG/opencode-game-studio --skill localize-traftg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Localization and internationalization in software projects require consistent string management, translation workflows, and verification to ensure UI quality across locales.

Core Features & Use Cases

  • Extract strings from source code and resource files to prepare translation keys.
  • Validate translations, detect missing keys, and ensure formatting and placeholders match.
  • Generate translation-ready string tables and report localization status for multiple locales.

Quick Start

Run the localization workflow with the subcommand you want (scan, extract, validate, or status) to begin managing localized strings.

Frequently Asked Questions about localize

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

FAQPage Schema
How do I extract strings from source code for translation?

To extract strings for translation, run the extract subcommand to scan source files in src/ and pull translatable text from your UI and documentation code, generating translation-ready string tables for your localization workflow.

How do I validate missing translation keys in my string tables?

You can validate missing translation keys by running the validate subcommand, which compares your source files against assets/data string tables to detect missing keys, verify formatting, and ensure placeholders match across multiple locales.

What is the best way to track localization status across multiple locales?

The best way to track localization status is using the status subcommand, which compares your src/ code against assets/data string tables to produce diffs for review, reporting on translation completeness for multiple locales.

Can I scan my codebase to find unlocalized UI and documentation strings?

Yes, you can scan your codebase to find unlocalized UI and documentation strings by running the scan subcommand, which reads source files from src/ and identifies translatable text missing from your string tables.

Do I need existing string tables in assets/data to compare with my source code?

Yes, you need existing string tables in assets/data to compare with your source code, as the localization workflow reads source files from src/ and diffs them against these tables to produce reports for review.