i18n-translations

Generate WordPress plugin POT files with WP-CLI i18n make-pot.

1|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/SilverAssist/contact-form-to-api --skill i18n-translations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-translations
Source: https://github.com/SilverAssist/contact-form-to-api/tree/main/.github/skills/i18n-translations
Command: npx skills add https://github.com/SilverAssist/contact-form-to-api --skill i18n-translations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating and updating the translation template (POT) for a WordPress plugin to ensure translators have current strings and avoiding localization drift.

Core Features & Use Cases

  • Generate or update the POT file for the plugin to capture all translatable strings across the codebase.
  • Integrate with PR workflows to ensure translations are up-to-date before submission.
  • Provide domain-consistent headers and metadata for translators.

Quick Start

Run WP-CLI i18n make-pot . languages/contact-form-to-api.pot --domain=contact-form-to-api and review changes before submitting.

Frequently Asked Questions about i18n-translations

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

FAQPage Schema
How do I generate a POT file for a WordPress plugin to capture translatable strings?

Generate a POT file by running WP-CLI i18n make-pot to scan the codebase for PHP gettext calls, producing a translation template with proper domain headers and excluding vendor directories.

Why does my WordPress plugin translation template drift from the actual codebase strings?

Translation template drift occurs when new or changed PHP gettext calls are not captured. Regenerating the POT file with WP-CLI i18n make-pot syncs the template with current strings.

Can I use WP-CLI i18n make-pot to update translations in a PR workflow?

Yes, you can integrate WP-CLI i18n make-pot into PR workflows to generate or update the POT file before submission, ensuring all translatable strings are captured and up-to-date.

Does WP-CLI i18n make-pot exclude vendor and node_modules directories when scanning for translatable strings?

Yes, the WP-CLI i18n make-pot process excludes vendor and node_modules directories, ensuring the translation template only captures strings from the plugin's own codebase.

What is the best way to maintain WordPress localization files and avoid localization drift?

Maintain WordPress localization files by regularly regenerating the POT template using WP-CLI i18n make-pot, which captures new translatable strings and prevents localization drift.