How do I install the I18N Completeness skill?

Run npx skillmds@latest add majiayu000/i18n-completeness-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is I18N Completeness safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with I18N Completeness?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is I18N Completeness free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published I18N Completeness?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

I18N Completeness by majiayu000 — Agent Skill

Name: I18N Completeness
Rating: 4.2 (5 reviews)
Author: majiayu000

I18N Completeness

Comprehensive i18n consistency check with dynamic pattern detection and hardcoded string analysis. Use when working with translations, localization, i18n keys, or when the user mentions translation issues, missing keys, or language support. Auto-triggers on phrases like "check translations", "i18n consistency", "localization issues", or "translation keys".

majiayu000 Updated Sep 22, 2026 567 repo stars

File contents

i18n Consistency Check & Cleanup

Comprehensive i18n analysis tool for the Tetris project supporting 2 languages (Japanese, English).

Quick Check

bun run check:i18n

Detection Capabilities

🔴 Missing Keys (Critical)

Keys used in code but not present in translation files
Priority: Critical (causes runtime errors)
Impact: Displays raw translation keys to users
Action: Add missing keys to all translation files immediately

📝 Hardcoded Strings (i18n Compliance)

User-facing strings not using t() function
Examples: "AI Replay", "Start AI", "Loading..."
Scope: Production code only (test files excluded)
Action: Convert to translation keys for proper localization

🔄 Dynamic Key Patterns (Analysis Required)

Template literal patterns like t(\game.${type}`)`
Analysis: Validates all possible key combinations exist
Action: Verify all generated keys are defined

⚠️ Unused Keys (Optimization)

Keys present in translation files but not used in code
Priority: Medium (cleanup opportunity)
Action: Remove unnecessary keys to optimize file size

Workflow

Execute Check: Run bun run check:i18n
Identify Issues: List Missing/Unused keys
Propose Fixes: Present specific correction methods
Confirm Execution: Ask user to approve modifications
Apply Fixes: Update translation files after approval
Verify: Re-run check after modifications

Translation Files

src/assets/locales/ja.json - Japanese translations (default)
src/assets/locales/en.json - English translations

Safety Measures

Re-verify usage before key deletion
Execute consistent operations across all language files
Validate JSON syntax after modifications
Confirm no issues with tests and build

When This Skill Activates

"Check translations"
"i18n consistency check"
"Are all translation keys defined?"
"Find hardcoded strings"
"Translation cleanup"
"Localization issues"
"Missing translation keys"

Advanced Usage

For detailed pattern detection and Serena MCP integration, see reference.md.

---name: i18n-completeness-2description: Comprehensive i18n consistency check with dynamic pattern detection and hardcoded string analysis. Use when working with translations, localization, i18n keys, or when the user mentions translation issues, missing keys, or language support. Auto-triggers on phrases like "check translations", "i18n consistency", "localization issues", or "translation keys".---# i18n Consistency Check & CleanupComprehensive i18n analysis tool for the Tetris project supporting 2 languages (Japanese, English).## Quick Check```bashbun run check:i18n```## Detection Capabilities### 🔴 Missing Keys (Critical)- Keys used in code but not present in translation files- **Priority**: Critical (causes runtime errors)- **Impact**: Displays raw translation keys to users- **Action**: Add missing keys to all translation files immediately### 📝 Hardcoded Strings (i18n Compliance)- User-facing strings not using `t()` function- **Examples**: "AI Replay", "Start AI", "Loading..."- **Scope**: Production code only (test files excluded)- **Action**: Convert to translation keys for proper localization### 🔄 Dynamic Key Patterns (Analysis Required)- Template literal patterns like `t(\`game.${type}\`)`- **Analysis**: Validates all possible key combinations exist- **Action**: Verify all generated keys are defined### ⚠️ Unused Keys (Optimization)- Keys present in translation files but not used in code- **Priority**: Medium (cleanup opportunity)- **Action**: Remove unnecessary keys to optimize file size## Workflow1. **Execute Check**: Run `bun run check:i18n`2. **Identify Issues**: List Missing/Unused keys3. **Propose Fixes**: Present specific correction methods4. **Confirm Execution**: Ask user to approve modifications5. **Apply Fixes**: Update translation files after approval6. **Verify**: Re-run check after modifications## Translation Files- `src/assets/locales/ja.json` - Japanese translations (default)- `src/assets/locales/en.json` - English translations## Safety Measures- Re-verify usage before key deletion- Execute consistent operations across all language files- Validate JSON syntax after modifications- Confirm no issues with tests and build## When This Skill Activates- "Check translations"- "i18n consistency check"- "Are all translation keys defined?"- "Find hardcoded strings"- "Translation cleanup"- "Localization issues"- "Missing translation keys"## Advanced UsageFor detailed pattern detection and Serena MCP integration, see [reference.md](reference.md).

Frequently asked questions