localization

Update Localizable.xcstrings translations after code changes via misc/translate.py.

105|10|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/everpcpc/KMReader --skill localization-everpcpc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localization
Source: https://github.com/everpcpc/KMReader/tree/main/.agents/skills/localization
Command: npx skills add https://github.com/everpcpc/KMReader --skill localization-everpcpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and stabilizes KMReader translations across locales by keeping Localizable.xcstrings up to date after code changes.

Core Features & Use Cases

  • Maintain and refresh Localizable.xcstrings after new strings are added or existing keys change.
  • Support deterministic updates via misc/translate.py with per-key checks and language completion.
  • Assist with missing key discovery and context lookup to reduce translation drift.

Quick Start

First, run a full build and then execute the localization workflow to synchronize translations.

Frequently Asked Questions about localization

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

FAQPage Schema
How do I keep Localizable.xcstrings in sync after adding new Swift strings?

To keep Localizable.xcstrings in sync, enforce a full project build before running the localization workflow. This ensures deterministic updates via misc/translate.py, capturing newly added keys and preventing translation drift across all supported languages.

What is the best way to automate iOS app translation workflows during a release cycle?

Automating iOS app translation workflows requires deterministic updates through misc/translate.py, which enforces a full build before localizing. This provides per-key checks and batch translation support to refresh languages accurately during development, QA, or release cycles.

How does the translate.py script handle missing translation keys and context lookup?

The translate.py script handles missing keys by assisting with missing key discovery and context lookup to reduce translation drift. It applies deterministic updates to Localizable.xcstrings, providing per-key checks and verifying language completion after code changes.

Do I need to run a full build before executing batch translation updates?

Yes, you need to run a full build before executing batch translation updates. The localization workflow strictly enforces a full build before localizing to ensure deterministic updates through misc/translate.py and maintain accurate Localizable.xcstrings synchronization.

Can I check individual translation completion status for specific languages?

Yes, you can check individual translation completion status because the workflow provides per-key checks and language completion support. By running the localization workflow via misc/translate.py, you verify that Localizable.xcstrings accurately reflects all required translations.