1
    i18n Completeness Auditor

    i18n Completeness Auditor

    Audit a JavaScript or TypeScript frontend for missing translations and hardcoded UI strings before you ship a new locale. Flags hardcoded JSX text and UI props (title, placeholder, aria-label, label, alt) not wrapped in t(), i18n.t(), or <Trans>; keys present in the default locale but missing from other locale files; keys referenced in code but absent from the locales (the raw dotted keys that leak to users); unused locale keys; and unparseable locale JSON.

    Updated Jun 2026
    Security scanned
    Cursor

    $12

    · or 60 credits

    30-day refund guarantee

    Secure checkout via Stripe

    Included in download

    • Identify user-facing text not wrapped in translation functions.
    • Locate translation keys used in code but missing from JSON files.
    • terminal, file_read automation included
    • Ready for Cursor
    • Instant install

    Sample input

    Audit my React app's frontend folder for any missing translations or hardcoded text in the components.

    Sample output

    ### i18n Audit Results **Rule: Hardcoded-Strings** - `src/components/Header.tsx:14`: "Welcome to the Dashboard" - `src/components/Footer.tsx:42`: "All rights reserved" **Rule: Missing-Keys** - `src/pages/Settings.tsx:22`: Key `settings.account.delete_confirm` not found in `en.json`.

    About This Skill

    Maintain Internationalization Quality with Ease

    Ensuring your application is fully localized is a tedious task for any developer. The i18n Completeness Auditor automates the hunt for hardcoded UI strings, missing translation keys, and orphaned entries across your codebase, saving you hours of manual grep-work and UI testing.

    What it does

    The skill scans your JavaScript and TypeScript source files (JS, JSX, TS, TSX) alongside your locale JSON files. It identifies four critical issues:

    • Hardcoded Strings: User-facing text not wrapped in translation helpers.
    • Missing Keys: Keys called in your code that don't exist in your locale files.
    • Orphaned Keys: Translated strings that are no longer used anywhere in the code.
    • Raw-Key Leakage: Heuristics for where keys might be displayed as raw strings to users.

    Why use this skill?

    Unlike basic string searching, this skill uses specific patterns to distinguish between code logic and UI text. It provides a structured audit report with file and line evidence, helping you achieve 100% translation coverage before a release. It works purely via file analysis, meaning no heavy build tools or external API dependencies are required.

    Supported Tech

    Supports modern frontend stacks including React, Vue, and Angular using standard i18n patterns. Optimized for JSON-based locale management.

    Use Cases

    • Identify user-facing text not wrapped in translation functions.
    • Locate translation keys used in code but missing from JSON files.
    • Clean up your locale files by finding unused translation keys.
    • Generate a checklist of i18n gaps for pre-release review.

    Reviews

    No reviews yet - be the first to share your experience.

    Only users who have downloaded or purchased this skill can leave a review.

    Security Scanned

    Passed automated security review

    Permissions

    Terminal / Shell
    Read Files

    File Scopes

    i18n-completeness-auditor/**
    **/*.js
    **/*.jsx
    **/*.ts
    **/*.tsx
    **/locales/**/*.json
    **/i18n/**/*.json

    Read-only. Parses locale JSON with the standard library and prints findings with rule id, severity, file, and line. Ignores node_modules, dist, build, .next, and coverage. Reads no environment variables.

    Works with any agent that can read a repo and run a local Python script (Claude Code, Cursor, Codex CLI, and other SKILL.md-compatible agents). Standard library only, no install step. Scans .js/.jsx/.ts/.tsx source plus JSON locale files under locales/ or i18n/. Read-only: it does not write or reorder translation files.

    Frequently Asked Questions

    $12