i18n-update

Scan WordPress plugin source files and update POT, PO, and MO language files.

12|9|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/jnealey88/designsetgo --skill i18n-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-update
Source: https://github.com/jnealey88/designsetgo/tree/main/.claude/skills/i18n-update
Command: npx skills add https://github.com/jnealey88/designsetgo --skill i18n-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The i18n-update skill helps plugin developers and maintainers keep their translations up to date by scanning source strings for untranslated content and updating language files accordingly.

Core Features & Use Cases

  • Scan code for missing translations and generate or update POT files.
  • Update existing PO/MO files across languages to reflect new strings.
  • Use case: A WordPress plugin with 5 active languages automatically synchronizes translations after code changes.

Quick Start

Run a translation workflow to scan the codebase and update language files.

Frequently Asked Questions about i18n-update

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

FAQPage Schema
How do I update WordPress plugin language files after code changes?

Update WordPress plugin language files by scanning source code for untranslated strings and synchronizing those changes into existing POT, PO, and MO files across all active languages.

What is the best way to scan source code for missing i18n strings?

Scanning source code for missing i18n strings involves parsing plugin files to identify gettext calls and generating a POT file that captures all translatable strings for multilingual synchronization.

Does i18n-update work with existing PO and MO translation files?

Yes, it works with existing PO and MO files by updating them in place to reflect new strings found during the source scan, ensuring translations stay current with the latest plugin code.

How do I generate a POT file for a WordPress plugin?

Generate a POT file for a WordPress plugin by running a translation workflow that scans the codebase to extract gettext strings and compiles them into a portable object template.

Can I automate translation synchronization across multiple plugin languages?

Automate translation synchronization across multiple plugin languages by running a workflow that detects code changes and updates the corresponding PO and MO files for each active language.

Why are my WordPress plugin translations out of sync with my code?

WordPress plugin translations fall out of sync when source code changes introduce new strings that are not propagated to existing PO and MO files, requiring a rescan to update the language files.