i18n-check

A pre-commit i18n check catches missing locale keys and untranslated strings before committing. It scans modified files for hardcoded labels, raw titles, and locale sync issues to prevent translation errors from reaching production.

The best way to check internationalization consistency in modified files is a focused i18n scan. It analyzes only changed files for hardcoded labels, raw PascalCase titles, and locale key inconsistencies to ensure translation completeness without checking the entire codebase.

Yes, you can auto-fix translation and locale key issues during a pre-commit scan by using the --fix mode. This automatically resolves detected internationalization inconsistencies in your modified files.

The i18n check scans just the changed files, not your entire project. This focused approach ensures fast execution by only analyzing modifications since the last commit, though you can specify a broader scope using --scope.

A pre-commit translation check catches hardcoded labels, raw PascalCase or camelCase titles, locale key sync issues, and missing locale infrastructure. It ensures your application's internationalization remains consistent and complete before code is committed.