skills.rest
agentik-os
agentik-osCOMMUNITY
Explore all skills by this author →
GitHub

i18naudit

Audit codebases for hardcoded strings, missing translation keys, and locale leakage.

10|3|Updated May 26, 2026
Search Tags:#formatting#audit#localization#i18n#internationalization#rtl#locale
One-click install
npx skills add https://github.com/agentik-os/OmegaOS --skill i18naudit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18naudit
Source: https://github.com/agentik-os/OmegaOS/tree/main/skills/audits/i18naudit
Command: npx skills add https://github.com/agentik-os/OmegaOS --skill i18naudit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forensic localization auditing helps teams identify and fix hardcoded strings, missing translations, and locale-related runtime leaks across products, ensuring consistent user experiences for all locales.

Core Features & Use Cases

  • 18-phase i18n audit covering hardcoded strings, key presence, framework wiring, locale routing, date/number/currency formatting, RTL support, and encoding.
  • Inventory and verification of declared locales, catalogs, and keys, with a hinge point to gate all translations.
  • Detailed, phase-aligned reports (hardcoded strings, framework wiring, locale routing, formatting, runtime leakage) and actionable fix plans for multi-language apps.
  • Example: A SaaS product shipping in en/fr/ar uses i18naudit to surface RTL issues, missing keys, and date formatting mismatches before release.

Quick Start

Run an i18naudit session against your codebase to produce a discovery report and a prioritized fix plan.

Frequently Asked Questions about i18naudit

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

FAQPage Schema
How do I audit my codebase for hardcoded strings and missing translation keys?▼

A forensic localization audit identifies hardcoded strings, missing translation keys, and runtime locale leakage across code, catalogs, and UI surfaces. It produces structured findings, a hinge-point map, and a fix plan for multi-language products.

What is runtime locale leakage and how does an internationalization audit detect it?▼

Runtime locale leakage occurs when locale-specific data crosses frontend and backend boundaries incorrectly. An i18n audit detects this by inventorying declared locales and verifying framework wiring, routing, and formatting across all surfaces.

How do I check my application for proper RTL support and CLDR pluralization before launch?▼

You check RTL support and CLDR pluralization by running an 18-phase i18n audit that evaluates locale routing, date, number, and currency formatting. It generates phase-aligned reports to ensure your product is world-ready.

Does this localization audit work across both frontend and backend boundaries?▼

Yes, the localization audit applies to multi-language products across frontend and backend boundaries. It verifies framework wiring, locale routing, and encoding, producing a prioritized fix plan and enabling a re-audit to confirm resolution.

What is the best way to fix locale-aware formatting mismatches in a SaaS product?▼

The best way to fix locale-aware formatting mismatches is running a forensic i18n audit to surface date and number formatting issues. It delivers a hinge-point map to gate all translations and an actionable fix plan.

Related Skills

Explore More Software Engineering Skills→
massCodeIOmassCodeIO
6.9k

i18n

Manage translation keys across en_US and ru_RU locales in massCode.

Official
Intermediate
grasberggrasberg
3

i18n-localization

Detect hardcoded strings and validate translation keys across React, Vue, and Python projects.

Community
Advanced
Celia-12Celia-12

translation

Translate text and documents with cultural adaptation and CLDR locale formatting.

Community
Intermediate
juniorfontenelejuniorfontenele

i18n-manager

Audit, fix, and synchronize translation files for Laravel and React applications.

Community
Advanced