Generate i18n Translation Files from Your Codebase
Managing translation files by hand is a recipe for missing keys and stale strings — let Claude scan your codebase and generate them for you.
cat src/**/*.tsx | claude -p "Find all hardcoded user-facing strings in this code and generate a complete en.json i18n file with appropriate translation keys. Group related keys by feature."
Once you have the base locale file, ask Claude to generate translations for additional languages:
cat locales/en.json | claude -p "Translate all values in this JSON to Spanish (es) and French (fr). Return two separate JSON objects, keeping the same key structure and respecting any {placeholder} variables."
Claude handles nested key structures, placeholder variables like {name}, and pluralization rules correctly. You can also ask it to audit an existing locale file against your source code to surface orphaned keys or missing translations:
# Find keys in your source that have no translation entry
claude -p "Compare these two files: my source code and my en.json. List any user-facing strings in the source that are missing from the locale file."
The result is a consistent, well-structured i18n setup you'd normally spend hours maintaining by hand.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.