skills.rest
petrSimonidesXart
petrSimonidesXartCOMMUNITY
Explore all skills by this author →
GitHub

i18n-glossary-sync

Compare translation terms across locales against a canonical i18n glossary.

Updated Mar 8, 2026
Search Tags:#consistency#audit#localization#glossary#i18n#translations
One-click install
npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill i18n-glossary-sync-petrsimonidesxart
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n-glossary-sync
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/cross/i18n-glossary-sync
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill i18n-glossary-sync-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translation terms often drift across locales, causing inconsistencies and wasted effort. This skill maintains a canonical i18n glossary file and automatically syncs new terms, detects drift, flags missing translations, and enforces terminology consistency across all language pairs.

Core Features & Use Cases

  • Glossary synchronization across en/fr/de/es to ensure uniform terminology.
  • Coverage and drift analysis: compare glossary definitions with actual translations to identify gaps and inconsistencies.
  • Proposals and governance: generate a glossary_update_proposal for manual review and update of domains/i18n/glossary.md.

Quick Start

Run the glossary sync to detect drift, analyze translations, and prepare glossary update proposals for the glossary.

Frequently Asked Questions about i18n-glossary-sync

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

FAQPage Schema
How do I sync i18n glossary terms across multiple locales?▼

To sync i18n glossary terms, the skill identifies all translation terms used across en/fr/de/es locales and compares them against a canonical glossary to flag inconsistencies and enforce a single source of truth for terminology.

What causes terminology drift in translations and how do I audit it?▼

Terminology drift in translations is caused by terms deviating across locales over time. You audit it by comparing actual localized content against a canonical glossary to detect gaps, track variants, and surface deprecated terms.

How do I find missing translations in my i18n glossary?▼

You find missing translations in your i18n glossary by running a coverage analysis that compares your glossary definitions with actual translations across en/fr/de/es, allowing the system to propose missing terms for manual review.

Can I generate proposals to update my localization glossary automatically?▼

You can generate proposals to update your localization glossary automatically. The skill outputs a structured glossary_update_proposal containing missing translations and flagged inconsistencies for manual review and governance.

Does this glossary synchronization approach support languages outside of en/fr/de/es?▼

This glossary synchronization approach does not natively support languages outside of en/fr/de/es. The skill is specifically configured to analyze terminology consistency and drift across only these four language pairs.

Related Skills

Explore More Content & Communication Skills→
bketelsenbketelsen
1

i18n-glossary-sync

Synchronize i18n glossary terms across language translation files.

Community
Advanced
teocraftersteocrafters

i18n-validation

Validate i18n translation keys across Polish and English locale files.

Official
Advanced
delta-and-betadelta-and-beta

engineer-localization

Integrate translation management systems with Braze for automated content localization.

Community
Advanced
foreveryhforeveryh
14

translator

Translate text across languages while preserving Markdown, code blocks, and tone.

Community
Basic