compare-i18n-keys

Compare Angular translate pipe keys with Transloco t() function keys.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Michael0520/milo-claudekit --skill compare-i18n-keys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compare-i18n-keys
Source: https://github.com/Michael0520/milo-claudekit/tree/main/plugins/one-ui-migration/skills/compare-i18n-keys
Command: npx skills add https://github.com/Michael0520/milo-claudekit --skill compare-i18n-keys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of migrating internationalization (i18n) keys between different translation systems, ensuring consistency and reducing manual errors.

Core Features & Use Cases

  • Key Comparison: Compares translation keys used in legacy Angular translate pipes with those in the new Transloco t() function.
  • Migration Assistance: Identifies missing or different keys, providing a clear report for manual review and correction.
  • Use Case: When migrating an Angular application from an older i18n library to Transloco, this Skill helps ensure all translation keys are correctly mapped and present in the new system.

Quick Start

Compare i18n keys between legacy file '/path/to/old/component.html' and new file '/path/to/new/component.html'.

Frequently Asked Questions about compare-i18n-keys

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compare i18n keys between Angular translate pipes and Transloco?

To compare i18n keys, specify the source and target file paths for your legacy Angular translate pipes and new Transloco t() functions. The comparison identifies discrepancies and missing keys, generating a clear report for manual review.

How do I find missing translation keys when migrating to Transloco?

Finding missing translation keys during Transloco migration requires comparing legacy Angular translate pipe usage against the new t() function calls. This Skill scans specified source and target HTML files to report any unmapped or missing i18n entries.

What is the best way to sync i18n keys across Angular projects?

Syncing i18n keys across Angular projects involves comparing translation definitions between legacy translate pipes and Transloco t() functions. This process highlights key discrepancies and missing entries to ensure complete translation parity.

Can I use this for Angular migration from older i18n libraries to Transloco?

Yes, this is designed specifically for Angular migration from older i18n libraries to Transloco. It compares your legacy translate pipe keys with the new Transloco t() function keys to ensure all translations are correctly mapped and present.

How does the i18n key comparison report work for manual review?

The i18n key comparison report works by analyzing specified source and target files to list discrepancies and missing keys between Angular translate pipes and Transloco. It provides a clear output for developers to manually correct unmapped translations.

Do I need specific file paths to compare Angular translation keys?

Yes, you must provide specific source and target file paths to compare Angular translation keys. The Skill requires these exact paths to scan legacy translate pipe usage and new Transloco t() function implementations for discrepancies.