From lokalise-pack
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".
How this skill is triggered — by the user, by Claude, or both
Slash command
/lokalise-pack:lokalise-ci-integrationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
@lokalise/cli2) or API SDKRead(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)| 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 |
#!/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"
See CI/CD implementation details for output format specifications.
npx claudepluginhub ktiseos-nyx/claude-code-plugins-plus-skills --plugin lokalise-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026