migrate-opslisted

# Migrate Operations Comprehensive migration skill covering framework upgrades, language version bumps, dependency auditing, breaking change detection, codemods, and rollback strategies. ## Migration Strategy Decision Tree ``` What kind of migration are you performing? │ ├─ Small library update (patch/minor version) │ └─ In-place upgrade │ Update dependency, run tests, deploy │ ├─ Major framework version (React 18→19, Vue 2→3, Laravel 10→11) │ │ │ ├─ Codebase < 50k LOC, good test coverage (>70%) │ │ └─ Big Bang Migration │ │ Upgrade everything at once in a feature branch │ │ Pros: clean cutover, no dual-version complexity │ │ Cons: high risk, long branch life, merge conflicts │ │ │ ├─ Codebase > 50k LOC, partial test coverage │ │ └─ Incremental Migration │ │ Upgrade module by module, use compatibility layers │ │ Pros: lower risk per step, continuous delivery │ │ Cons: dual-version code, longer total duration │ │ │ ├─ Monolith → microservice or complete architecture shift │ │ └─ Strangler Fig Pattern │ │ Route new features to new system, migrate old features gradually │ │ Pros: zero-downtime, reversible, production-validated │ │ Cons: routing complexity, data sync challenges │ │ │ └─ High-risk data pipeline or financial system │ └─ Parallel Run │ Run old and new systems simultaneously, compare outputs │ Pros: highest confidence, catch subtle differences │ Cons: double infrastructure cos