migration-review

Compare TypeScript and HTML code migration completeness between source and target directories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the tedious and error-prone process of manually comparing codebases to ensure that all necessary components, logic, and UI elements have been successfully migrated from an old system to a new one.

Core Features & Use Cases

  • Comprehensive Code Comparison: Analyzes form controls, validators, HTML elements, and UI guidelines between source and target code paths.
  • Automated UI Guideline Checks: Identifies and can auto-fix common UI guideline violations, ensuring consistency and adherence to standards.
  • Use Case: After migrating a large Angular application from version 16 to 20, use this Skill to verify that all form fields, their validations, and specific UI components like buttons and dialogs have been correctly translated to the new architecture.

Quick Start

Use the migration-review skill to compare the old code at '/path/to/old/code' with the new code at '/path/to/new/code'.

Frequently Asked Questions about migration-review

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

FAQPage Schema
How do I verify Angular migration completeness between source and target directories?

To verify Angular migration completeness, compare source and target directories to analyze form controls, validators, and HTML elements. This process identifies discrepancies and enforces UI guideline compliance to ensure all components are successfully migrated.

What is the best way to check for missing form validators after a codebase migration?

The best way to check for missing form validators is to perform a detailed comparison of TypeScript and HTML files between the old and new code paths. This highlights missing validation logic and potential architectural discrepancies in the migrated code.

Can I automatically fix UI guideline violations during a code comparison?

Yes, you can automatically fix specific UI guideline violations during a code comparison. The analysis supports automated fixing of elements like button types and enforces architectural patterns for dialogs, tables, and page layouts.

Does the code migration review process generate a report of potential issues?

Yes, the code migration review process generates a comprehensive markdown report detailing findings and areas for improvement. This report covers discrepancies in form controls, HTML elements, and UI guideline compliance identified during the comparison.

How do I review refactored HTML elements and TypeScript files to ensure UI standards?

Review refactored HTML elements and TypeScript files by running an automated check against UI guidelines. This identifies inconsistencies and enforces architectural patterns for dialogs and page layouts, ensuring the refactored code meets required standards.