Back to skills
SKILL.md
Lokalise Ci Integration
ASecurityConfigure Lokalise CI/CD integration with GitHub Actions and automated sync. Use when setting up automated translation sync, configuring CI pipelines, or integrating Lokalise into your build process. Trigger with phrases like "lokalise CI", "lokalise GitHub Actions", "lokalise automated sync", "CI lokalise", "lokalise pipeline".
- 4 stars
- 0 votes
- 0 copies
- 3 views
- Added September 10, 2026
Works with
Security analysis
100/100Pro scans all 3 files and shows the line behind each finding
npx -y skills add micsapp/micstec-skills --skill lokalise-ci-integration --agent claude-codeAre you the author of Lokalise Ci Integration?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/micsapp-lokalise-ci-integration)---
name: lokalise-ci-integration
description: |
Configure Lokalise CI/CD integration with GitHub Actions and automated sync.
Use when setting up automated translation sync, configuring CI pipelines,
or integrating Lokalise into your build process.
Trigger with phrases like "lokalise CI", "lokalise GitHub Actions",
"lokalise automated sync", "CI lokalise", "lokalise pipeline".
allowed-tools: Read, Write, Edit, Bash(gh:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Lokalise CI Integration
## Overview
Automate translation workflows with Lokalise in CI/CD pipelines. Covers pushing source strings on merge, pulling translations before builds, validating translation completeness, and webhook-triggered deployments.
## Prerequisites
- Lokalise API token stored as GitHub secret
- Lokalise CLI (`@lokalise/cli2`) or API SDK
- GitHub Actions configured
- Project ID identified
## Instructions
1. For full implementation details, load: `Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)`
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Upload fails | Invalid JSON | Validate locale files before push |
| Missing translations | Download with empty strings | Use `--export-empty-as skip` |
| Webhook not triggered | Dispatcher not configured | Set up Lokalise webhook to GitHub |
| Wrong file structure | Prefix mismatch | Use `--directory-prefix ""` in download |
## Examples
### Local Translation Script
```bash
#!/bin/bash
# scripts/lokalise-pull.sh
lokalise2 file download \
--token "$LOKALISE_API_TOKEN" \
--project-id "$LOKALISE_PROJECT_ID" \
--format json \
--unzip-to "src/locales/"
echo "Translations updated"
```
## Resources
- [Lokalise CLI Reference](https://docs.lokalise.com/cli2)
- [Lokalise GitHub Actions](https://docs.lokalise.com/integrations/github)
- [Lokalise Webhooks](https://docs.lokalise.com/webhooks)
## Output
- Configuration files or code changes applied to the project
- Validation report confirming correct implementation
- Summary of changes made and their rationale
See [CI/CD implementation details](${CLAUDE_SKILL_DIR}/references/implementation.md) for output format specifications.Files in this skill
- SKILL.md
- references/implementation-guide.md
- references/implementation.md
Attribution
Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.