i18n-validation

Name: i18n-validation
Availability: InStock
Author: teocrafters

Validate i18n translation keys across Polish and English locale files.

Updated Aug 29, 2025

Search Tags:#validation #i18n #translation-keys #locales #en.json #commit-check #pl.json

Ready to run

npx skills add https://github.com/teocrafters/public-talk-planner --skill i18n-validation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n-validation
Source: https://github.com/teocrafters/public-talk-planner/tree/main/.claude/skills/i18n-validation
Command: npx skills add https://github.com/teocrafters/public-talk-planner --skill i18n-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams prevent missing translations by verifying that new i18n keys exist in both Polish (pl.json) and English (en.json) locale files before commits. It ensures that all user-facing text remains properly localized and reduces runtime translation errors.

Core Features & Use Cases

Validate newly introduced i18n keys across pl.json and en.json.
Detect missing or empty keys, and flag mismatches in key paths.
Integrate into pre-commit or CI workflows to enforce localization quality.

Quick Start

Run a quick validation on your codebase to ensure new i18n keys are present in both locale files before committing.

Frequently Asked Questions about i18n-validation

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

FAQPage Schema

How do I validate i18n translation keys across locale files before a commit?▼

To validate i18n translation keys before a commit, this skill checks new keys in pl.json and en.json to ensure path consistency and non-empty values, preventing missing translations.

What is the best way to prevent missing i18n keys in Polish and English locale files?▼

The best way to prevent missing i18n keys in Polish and English locales is to enforce key existence and validate path consistency across pl.json and en.json during development or CI processes.

Can I integrate i18n locale validation into my CI workflow?▼

Yes, you can integrate i18n locale validation into CI workflows to enforce localization quality by automatically detecting missing or empty keys and flagging mismatches in translation paths.

Does i18n validation work with JSON locale files for code review?▼

Yes, i18n validation works with JSON locale files during code review by verifying that newly introduced translation keys exist in both pl.json and en.json and contain non-empty values.

Why are my translation keys showing missing path mismatches between locales?▼

Translation keys show missing path mismatches between locales when new UI text keys are added to one locale file but not properly mirrored in the corresponding pl.json or en.json files.