orbit-i18n-js-parity

Verify PHP-emitted JavaScript label keys for parity using grep and diff.

2|1|Updated Apr 20, 2026

Search Tags:#translation #JavaScript #PHP #label parity #i18n audit

Ready to run

npx skills add https://github.com/adityaarsharma/orbit --skill orbit-i18n-js-parity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orbit-i18n-js-parity
Source: https://github.com/adityaarsharma/orbit/tree/main/skills/orbit-i18n-js-parity
Command: npx skills add https://github.com/adityaarsharma/orbit --skill orbit-i18n-js-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill identifies and prevents silent English fallbacks by ensuring every label key consumed by JavaScript is actually emitted from PHP.

Core Features & Use Cases

Label Parity Audit: Verifies PHP-localized JS labels to avoid missing translations.
Bug Detection: Identifies missing translations where JavaScript reads keys not emitted by PHP.
Plugin-Agnostic: Applies to any plugin with PHP-localized JS labels, including Elementor, Gutenberg, and admin JS.

Quick Start

Run the orbit-i18n-js-parity skill to audit your plugin for label parity issues.

Frequently Asked Questions about orbit-i18n-js-parity

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

FAQPage Schema

How do I check PHP and JavaScript label parity to prevent missing translations?▼

To prevent silent English fallbacks, verify PHP-localized JavaScript label parity by scanning JavaScript object consumption and PHP emission using grep and diff. This detects missing keys where JavaScript reads labels not emitted by PHP.

Why does my JavaScript fall back to English when PHP translations exist?▼

JavaScript falls back to English when it consumes label keys that PHP does not actually emit. Running a label parity audit compares the consumed JS keys against the emitted PHP keys to find and fix these exact mismatches.

Does this label parity audit work with Gutenberg and Elementor plugins?▼

Yes, the label parity audit is plugin-agnostic and works with any plugin utilizing PHP-localized JS labels, including Gutenberg, Elementor, and custom admin JavaScript, ensuring all consumed keys are properly emitted.

What tools do I need to scan for missing i18n keys in my codebase?▼

You need grep and diff to scan for missing i18n keys. The process uses grep to extract JavaScript object name consumption and PHP emission, then applies diff to compare the extracted lists and identify label parity issues.

How do I detect silent English fallbacks in my localized JavaScript?▼

Detect silent English fallbacks by running a parity audit that verifies every JavaScript label key has a corresponding PHP emission. It highlights consumed JS keys that lack PHP translation emission, preventing missing translation bugs.