Agent skill · software engineering · jeremylongshore
lokalise-ci-integration
Configure Lokalise CI/CD integration with GitHub Actions and automated
Why this skill is useful
Adds executable scripts for automated translation sync with Lokalise using GitHub Actions, which are not commonly found in public documentation.
What it needs
Requires lokalise-cli installed locally. Requires lokalise account access. About 6k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lokalise CI Integration Overview Automate the full translation lifecycle through GitHub Actions: upload source strings when code is pushed, download translations during builds, block PRs with missing translations, and manage branch-based translation workflows that mirror your Git branching strategy. The goal is zero manual translation file management — developers write code, translators work in Lokalise, and CI keeps everything in sync. Prerequisites Lokalise project with Project ID (Settings > General > Project ID) Lokalise API token with read/write permissions (Profile > API Tokens), stored as LOKALISEAPITOKEN GitHub secret LOKALISEPROJECTID stored as GitHub secret (or variable) Lokalise CLI v2 (lokalise2) — installed in CI via curl -sfL https://raw.githubusercontent.com/nicktomlin/lokalise-cli-2-install/master/install.sh sh Source locale files committed to the repository (e.g., src/locales/en.json) Instructions Step 1: Upload Source Strings on Push Create .github/workflows/lokalise-upload.yml to push source strings to Lokalise whenever the default locale file changes on main: Step 2: Download Translations During Build Create .github/workflows/lokalise-build.yml or add a step to your existing build workflow: Step 3: PR Check for Missing Translations Add a workflow that comments on PRs when new translation keys lack translations in required locales: Step 4: Integration Tests for Key Coverage Add a test that validates translation files have all required keys at build time: Step 5: Branch-Based Translation Workflow Use Lokalise branching to isolate translation work per feature branch. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-ci-integration