localize

Automate game localization pipelines from string extraction to QA reports.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill localize-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/localize
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill localize-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Localization often fails when string extraction, translation briefs, cultural review, VO integration, and QA are treated as disconnected tasks; this Skill centralizes and automates the full pipeline so translations are accurate, context-aware, and release-ready.

Core Features & Use Cases

  • Scan & Extract: Find hardcoded user-facing strings, flag anti-patterns, and generate keyed string-table diffs ready for translator review.
  • Validate & QA: Check translations for completeness, placeholder mismatches, length violations, plural forms, encoding, and produce per-locale QA verdicts.
  • Localization Deliverables: Produce translator briefs, cultural review reports, VO recording manifests/scripts, RTL check reports, and manage string freeze lifecycles for a reliable handoff to vendors.

Quick Start

Use the localize skill in extract mode to scan the repository and propose new string-table entries for assets/data/strings/strings-en.json.

Frequently Asked Questions about localize

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

FAQPage Schema
How do I extract hardcoded strings from game source files for localization?

String extraction scans game repositories to find hardcoded user-facing text in UI and narrative files, flags anti-patterns, and generates keyed string-table diffs ready for translator review.

What is the best way to automate game localization validation and QA?

Game localization validation checks translations for completeness, placeholder mismatches, length violations, plural forms, and encoding errors, producing per-locale QA verdicts to ensure release-ready output.

How do I generate translator briefs and cultural review reports for game i18n?

Game i18n pipelines generate translator briefs and cultural review reports by scanning source strings and assets, providing context-aware documentation for reliable handoff to localization vendors.

Can I manage voice-over recording manifests and RTL checks within an automated localization pipeline?

Automated localization pipelines manage VO manifests and recording scripts alongside RTL check reports, integrating audio asset tracking and right-to-left text validation into a single workflow.

What file paths and repository access do I need to run an end-to-end game localization pipeline?

Game localization pipelines require read and write access to src/, assets/data/strings/, and production/localization/ directories, plus file search and diffing capabilities to produce diffs and reports.

Why does game localization fail when string extraction and QA are treated as disconnected tasks?

Game localization fails when tasks are disconnected because string extraction, cultural review, VO integration, and QA become misaligned; centralizing the full pipeline ensures translations are accurate, context-aware, and release-ready.