Best fit
Finds hardcoded UI strings, missing translation keys, and unused keys in a JavaScript or TypeScript frontend.
// frontend
i18n Completeness Auditor
Audit a JavaScript or TypeScript frontend for missing translations and hardcoded UI strings before you ship a new locale.
What it flags
- Hardcoded JSX text and UI props not wrapped in a translation call.
- Keys in the default locale but missing from others.
- Keys referenced in code but absent from the locales (the raw keys that leak to users).
- Unused locale keys.
- Unparseable locale JSON.
How to run
Point it at your source and locale files. Read-only.
Good to know
Heuristic. It recognizes t(), i18n.t(), and Trans as translation calls; custom wrappers may need a manual pass.
// choose with context
Is i18n Completeness Auditor the right skill?
It returns
Finds hardcoded UI strings, missing translation keys, and unused keys in a JavaScript or TypeScript frontend.
Do not use it as
Do not treat a successful run as proof beyond the supplied files, declared scope, and evidence the skill actually checked.
Compatibility, access, version, and licence
- Reads or accesses
- Only the files or context you deliberately provide; review the listing before granting additional access.
- Compatibility
- Agents that read the open SKILL.md format. Verify runtime and service requirements at the purchase or install destination.
- Version
- Verify the current package version at the linked destination.
- Licence
- Review the package licence and seller terms at the linked destination.
Questions
What is the worst bug it catches?
A missing key falling back to a raw dotted string shown to users.
Does it change anything?
No. It is read-only and flags issues for you to act on.
Ship a locale that is actually complete.
Current price and purchase option are shown on Agensi. Instant download. Works with any agent that reads SKILL.md.
Get i18n Completeness Auditor on Agensi