migration-upgrade

Produce end-to-end migration plans with assessment, execution, verification, and rollback.

Updated May 6, 2026
One-click install
npx skills add https://github.com/korwlik23/skills --skill migration-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-upgrade
Source: https://github.com/korwlik23/skills/tree/main/v1/migration-upgrade
Command: npx skills add https://github.com/korwlik23/skills --skill migration-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the risk of framework and dependency upgrades by enforcing an evidence-first process, incremental execution, rollback planning, and post-upgrade verification.

Core Features & Use Cases

  • Upgrade assessment and planning: Audits current versions, researches official migration guides and changelogs, and produces a structured upgrade plan with prerequisites, steps, and a timeline.
  • Safe execution and change management: Uses a dedicated branch, snapshots dependencies/lockfiles, applies an upgrade order (framework → official packages → third-party → dev deps → custom/config → data migrations), and avoids mixing upgrades with feature work.
  • Verification and data migration guardrails: Defines post-upgrade acceptance gates, smoke/E2E expectations, and data migration rules (idempotency, backups, production-size testing, validation, rollback readiness).

Use case: upgrade a Next.js or Laravel application across a major version while handling breaking changes and ensuring tests and critical flows still work before deployment.

Quick Start

Use this skill to produce a full migration report and step-by-step upgrade plan for upgrading your app from version X to version Y, including breaking changes, risk assessment, and a rollback strategy.

Frequently Asked Questions about migration-upgrade

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

FAQPage Schema
How do I plan a major framework upgrade without breaking existing code?

A safe framework upgrade requires reading official changelogs first, then upgrading incrementally in a specific order: framework, official packages, third-party dependencies, dev dependencies, and finally applying custom config or data migrations.

What is the best way to handle breaking changes during a dependency upgrade?

To handle breaking changes during a dependency upgrade, isolate the work on a dedicated branch, snapshot lockfiles, and apply a strict upgrade order from framework to dev dependencies without mixing feature work.

How does data migration verification work when moving across major version gaps?

Data migration verification enforces idempotent practices, requires backups, and mandates production-size testing. You define post-upgrade acceptance gates, smoke or end-to-end expectations, and validation rules to ensure rollback readiness.

Can I use this migration planning process for both minor and major version upgrades?

Yes, this migration planning process applies to both minor and major version gaps. It scales from handling deprecations to full tech stack migrations by enforcing incremental execution, verification testing, and proportional reporting.

What should be in a rollback plan when upgrading a web application framework?

A rollback plan for a framework upgrade must include dependency and lockfile snapshots, data backups, andDefined rollback readiness rules. These are established alongside post-upgrade acceptance gates and smoke or end-to-end validation expectations.