migrate-analyze

Migration gap analysis compares your repository against a standards document like coding_guidelines.md to identify architectural, naming, testing, and documentation deviations. It categorizes gaps by severity, estimates effort, and generates prioritized migration briefs.

A migration roadmap sequences codebase upgrades by organizing MG-XXX briefs into dependency-aware phases. It uses severity levels, affected file counts, and effort estimates (S/M/L/XL) to prioritize gaps so teams can execute staged migrations safely.

Migration briefs are generated non-destructively by analyzing your repository against target standards. The process outputs categorized gap briefs with severity scores and dependency ordering for review, while never changing or writing to your source files.

Yes, migration analysis applies to repositories with a coding_guidelines.md file or accepts a provided alternate base repo. It compares your project against whichever standards source you supply to surface deviations and plan the migration roadmap.

Migration gap analysis identifies architectural deviations, naming convention violations, testing gaps, and documentation inconsistencies. It surfaces these deviations from your codebase against the target standards document, categorizing each by severity and estimating remediation effort.