skills.rest
moongci38-oss
moongci38-ossCOMMUNITY
Explore all skills by this author →
GitHub

migration-audit

Audit code migration consistency between legacy and new stacks.

Updated Jun 3, 2026
Search Tags:#code audit#code migration#legacy code#code comparison#migration audit
One-click install
npx skills add https://github.com/moongci38-oss/forge-plugins --skill migration-audit-moongci38-oss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration-audit
Source: https://github.com/moongci38-oss/forge-plugins/tree/main/forge-core/skills/migration-audit
Command: npx skills add https://github.com/moongci38-oss/forge-plugins --skill migration-audit-moongci38-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of auditing legacy code migration to new stacks, ensuring consistency and identifying potential issues before production deployment.

Core Features & Use Cases

  • Automated Audit Process: Automates a 7-phase audit process to check for migration drifts, identify legacy bugs, and ensure compatibility.
  • Code Comparison: Compares legacy code with new code to identify discrepancies.
  • Use Case: This Skill is ideal for developers and QA teams working on migrating legacy systems to new technologies, ensuring a smooth transition with minimal issues.

Quick Start

Run the migration audit skill by executing '/migration-audit <legacy-path> <migrated-path> --stack=node-nest'.

Frequently Asked Questions about migration-audit

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

FAQPage Schema
How do I automate a legacy code migration audit?▼

Automate a legacy code migration audit by running a 7-phase process that checks for migration drifts, identifies legacy bugs, and ensures compatibility before production deployment.

What is code migration drift and how do I detect it?▼

Code migration drift refers to discrepancies between legacy and new stacks. Detect migration drift by comparing the legacy code with the new code to identify inconsistencies and potential issues.

Do I need git and npm to run a migration audit?▼

Yes, you need git and npm installed in your environment to run the migration audit, as the process requires specific scripts for executing the automated code comparison.

Can I audit a migration to a node-nest stack?▼

Yes, you can audit a migration to a node-nest stack by executing the audit command with the --stack=node-nest parameter, passing both your legacy and migrated code paths.

What's the best way to compare legacy code with new code?▼

The best way to compare legacy code with new code is using an automated 7-phase audit process that identifies discrepancies, detects migration drifts, and ensures the new code remains consistent.

Related Skills

Explore More Software Engineering Skills→
afsjrafsjr

reversa-paradigm-advisor

Detect legacy programming paradigms from migration specs and write paradigm_decision.md.

Community
Advanced
JDL440JDL440

Editorial Controls Split Migration

Migrate legacy depth_level to split editorial control fields across UI surfaces.

Community
Advanced
burgebjburgebj

ship

Automate testing, code review, pull request creation, and deployment workflows.

Community
Advanced
mymx2mymx2
4

sql-parser-cst

Parse SQL statements into a Concrete Syntax Tree preserving comments and whitespace.

Community
Advanced