i18n-check

Identify internationalization issues in code across file scopes and UI surfaces.

5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill i18n-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-check
Source: https://github.com/hereinthehive/gotrino-inclusion/tree/main/skills/i18n-check
Command: npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill i18n-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyzes code for internationalization issues to ensure UI text, formats, and flows work for diverse global audiences and locales.

Core Features & Use Cases

  • Contextual analysis of UI strings, dates, numbers, and layouts to identify i18n gaps.
  • Config-aware checks that respect .inclusion-config.md to honor project scope and decisions.
  • Practical workflows for code reviews and audits across web and app codebases to prepare for global release.
  • Use Case: A developer reviews a React app to find hard-coded strings, RTL layout problems, and missing translations to improve global readiness.

Quick Start

Inspect your codebase with i18n checks to surface internationalization gaps.

Frequently Asked Questions about i18n-check

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

FAQPage Schema
How do I find hard-coded strings and i18n gaps in my codebase?

To find hard-coded strings and i18n gaps, you analyze your codebase to surface internationalization issues across file scopes, components, and UI surfaces, determining their impact on diverse global audiences and locales.

What is the best way to check for RTL layout problems before a global release?

Checking for RTL layout problems involves performing contextual analysis of UI strings, dates, numbers, and layouts. This identifies i18n gaps and ensures flows work for diverse locales during code reviews and audits before global release.

Does i18n checking work with project configuration files?

Yes, i18n checks are config-aware and respect .inclusion-config.md files. This integration honors project scope and decisions, ensuring the analysis applies established patterns to enforce requirements like locale awareness without breaking translations.

How do I audit a React app for missing translations and locale awareness?

You audit a React app for missing translations by applying i18n checks across web codebases. This enforces locale awareness requirements and identifies non-breaking translation patterns using established project workflows.

When do I need to run internationalization checks on my UI components?

You need to run internationalization checks when preparing UI components for global audiences. The analysis identifies issues with UI text, formats, and flows, assessing their impact on diverse user contexts and ensuring readiness.

Can I enforce non-breaking translations during a code review?

Yes, you can enforce non-breaking translations during a code review. The analysis applies established patterns to ensure config integration, locale awareness, and non-breaking translations across the audited components.