Bilingual Release QA — JSON Translation Checks

English listing

A translated message can read correctly and still break your interface. Bilingual Release QA checks paired JSON locales for missing keys, empty messages, malformed ICU/i18next syntax and changed variables, tags or supported branch identities.

For developers and SaaS agencies releasing bilingual interfaces, especially English/French. Review terminology with your own glossary, then prepare a patch and a corrected target copy. Exact input hashes prevent a patch being applied to a different release.

You receive: HTML/Markdown/JSON reports, CSV findings, a patch template and, when corrections are requested, the reviewed patch and corrected JSON. Original files remain untouched. Includes fictional before/after examples.

Requirements: your own skill-capable agent with files and command execution, Node.js 22.13+ and the declared npm dependency. Object-namespaced JSON with string leaves; ICU or common i18next interpolation syntax. No publisher-operated hosting or model credits are included.

Limits: this is structural QA plus agent-assisted linguistic review, not certified translation or automatic language detection. Arrays, YAML, PO, code extraction, i18next plugin behavior, separate plural/context key families and live layout checks are outside this version. Locale-specific plural coverage, meaning and runtime date/currency behavior require review.

One-time launch price proposal: US$29.
Support: [email protected].
Scripts do not call the publisher or an external model; your invoking agent may send translations to your configured AI provider.