preen-i18n

Audit i18n coverage and detect missing translations and hardcoded strings.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/a2f0/tearleads --skill preen-i18n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preen-i18n
Source: https://github.com/a2f0/tearleads/tree/main/.codex/skills/preen-i18n
Command: npx skills add https://github.com/a2f0/tearleads --skill preen-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill proactively identifies and helps fix internationalization (i18n) issues within a project, such as missing translations, hardcoded strings, and inconsistencies across different languages.

Core Features & Use Cases

  • Translation Coverage Auditing: Detects missing translations and ensures consistency across all supported languages.
  • Hardcoded String Detection: Identifies instances where text is directly embedded in the code instead of using translation keys.
  • Type/Key Mismatch Analysis: Flags discrepancies between translation keys used in code and those defined in translation files.
  • Use Case: Before releasing a new feature, run this skill to ensure all user-facing text is properly internationalized, preventing a poor experience for non-English speaking users.

Quick Start

Run the preen i18n skill to check for translation coverage issues in the codebase.

Frequently Asked Questions about preen-i18n

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

FAQPage Schema
How do I detect hardcoded strings in my UI code for internationalization?

To detect hardcoded strings in UI elements and attributes for internationalization, you can run an automated TypeScript script that audits your codebase and reports text directly embedded in code instead of using translation keys.

What is the best way to find missing translations across multiple languages?

The best way to find missing translations is by running an internationalization coverage audit that analyzes translation files across multiple languages, detecting gaps and ensuring consistency for all supported locales.

How do I check for mismatches between translation keys and type definitions?

You can check for mismatches between translation keys and type definitions by running an automated consistency analysis that flags discrepancies between the keys used in your code and those defined in your translation files.

Can I integrate i18n auditing into my CI pipeline for quality assurance?

Yes, you can integrate i18n auditing into your CI pipeline for quality assurance, utilizing a TypeScript script that provides automated analysis and reporting to prevent missing translations before a release.

Why does my application show untranslated text for non-English speaking users?

Your application shows untranslated text because of missing internationalization coverage, where hardcoded strings or missing translation keys bypass the localization layer and display raw text to non-English speaking users.

Do I need TypeScript to audit my project's internationalization coverage?

Yes, you need a TypeScript environment to utilize the automated analysis script that audits internationalization coverage, detects hardcoded strings, and checks for type definition mismatches across your project.