locize-sync

Synchronize English and Chinese translations between the codebase and Locize.

515|208|Updated Jul 6, 2015
One-click install
npx skills add https://github.com/Opentrons/opentrons --skill locize-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: locize-sync
Source: https://github.com/Opentrons/opentrons/tree/main/.cursor/skills/locize-sync
Command: npx skills add https://github.com/Opentrons/opentrons --skill locize-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Localization workflows across the Opentrons monorepo are simplified by automating the push and pull of translations between local files and Locize. This skill coordinates a cohesive i18n pipeline using a central Python script, enabling teams to keep English and Chinese translations in sync with the cloud service.

Core Features & Use Cases

  • Push Local Translations: Upload English and Chinese translations to Locize, consolidating component translations into app-level localization before syncing.
  • Download Remote Translations: Retrieve updated translations from Locize and apply them locally, overwriting existing files in app/src/assets/localization/ and components/src/assets/localization/.
  • Dry-Run & Safety: Preview actions without applying changes using --dry-run, and validate environment variables (LOCIZE_API_KEY, LOCIZE_PROJECT_ID) before operations.
  • CI/CD & Automation: Integrate Locize sync into automated workflows for release pipelines; supports both push and download directions for multi-language teams.

Quick Start

Run uv run scripts/locize_sync.py push-local --dry-run to preview translations that would be uploaded.

Frequently Asked Questions about locize-sync

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

FAQPage Schema
How do I sync translations between a monorepo and Locize?

To sync translations with Locize, run the locize_sync.py script to push local English and Chinese translations or download remote updates directly into app and components asset directories within the monorepo.

What environment variables do I need to automate i18n localization with Locize?

Automating i18n localization requires setting the LOCIZE_API_KEY and LOCIZE_PROJECT_ID environment variables to authenticate API requests before pushing or downloading translations.

Can I preview translation changes before overwriting localization files in my monorepo?

Yes, you can preview translation changes by running the push-local command with the --dry-run flag to view pending uploads without modifying any remote or local localization files.

How do I download remote translations from Locize into specific monorepo directories?

Downloading remote translations from Locize overwrites existing localization files in app/src/assets/localization/ and components/src/assets/localization/ to ensure local codebases match the latest cloud updates.

Does Locize translation sync support CI/CD pipeline integration for multi-language teams?

Locize translation sync supports CI/CD integration by executing push and download commands within automated release pipelines to continuously update multi-language translations.

How are component-level translations consolidated before uploading to Locize?

Component-level translations are consolidated into app-level localization files before uploading to Locize, ensuring the entire monorepo's i18n assets are unified during the push workflow.