verify-legacy-with-qa-testcases

Compare legacy code against QA test cases and generate a Traditional Chinese verification report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the crucial step of verifying that legacy code accurately reflects the requirements defined in new QA test cases, ensuring a smooth and complete migration.

Core Features & Use Cases

  • Automated Code Comparison: Compares legacy code against detailed QA test cases to identify discrepancies.
  • Comprehensive Reporting: Generates a detailed report in Traditional Chinese, highlighting verified, missing, and partially implemented features.
  • Use Case: Before migrating a complex user authentication module, use this Skill to ensure all existing validation rules, error messages, and conditional display logic in the old code match the new requirements, preventing post-migration bugs.

Quick Start

Run the verify-legacy-with-qa-testcases skill with the path to the legacy code you want to verify.

Frequently Asked Questions about verify-legacy-with-qa-testcases

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

FAQPage Schema
How do I verify legacy code against new QA test cases before migration?

To verify legacy code against new QA test cases, this Skill analyzes form fields, validation rules, error messages, conditional display, API payloads, boundary cases, and interaction flows. It generates a detailed verification report confirming migration completeness and identifying discrepancies.

What is the best way to check legacy code for missing validation rules during a migration?

Checking legacy code for missing validation rules during a migration is handled by comparing legacy code against detailed QA test cases. This Skill identifies verified, missing, and partially implemented features to prevent post-migration bugs.

Can I generate a verification report for legacy code migration in Traditional Chinese?

Yes, you can generate a verification report for legacy code migration in Traditional Chinese. The Skill outputs a comprehensive report highlighting verified, missing, and partially implemented features, and identifying potential migration issues.

Does this legacy code verification tool require any external dependencies?

No, this legacy code verification tool does not require any external dependencies. You can run the Skill directly with the path to your legacy code to start the automated code comparison and reporting process.

How do I test legacy code API payloads and boundary cases against new requirements?

To test legacy code API payloads and boundary cases against new requirements, the Skill automates code comparison by analyzing these specific interaction flows. It confirms whether the old code matches the new QA test case definitions.