skills.rest
EvanPluchart
EvanPluchartCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

migration-planner

Analyze breaking changes and generate progressive migration plans for software stacks.

2|Updated Mar 19, 2026
Search Tags:#rollback#migration#breaking changes#upgrade planning#batch execution#CI verification
One-click install
npx skills add https://github.com/EvanPluchart/kyomu --skill migration-planner-evanpluchart
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration-planner
Source: https://github.com/EvanPluchart/kyomu/tree/main/.claude/skills/migration-planner
Command: npx skills add https://github.com/EvanPluchart/kyomu --skill migration-planner-evanpluchart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the risk of big-bang upgrades by analyzing breaking changes and producing a progressive migration plan with verification and rollback.

Core Features & Use Cases

  • Analyze breaking changes: Scans the project, maps impacted files/APIs/imports, classifies changes (automatic / semi-automatic / manual), and estimates effort.
  • Generate a migration plan: Builds an ordered, dependency-aware batch plan (prep → functional batches → cleanup) including rollback strategy and go/no-go criteria.
  • Execute with guardrails: Applies changes lot by lot, verifies types/build/tests/visual checks, and creates atomic commits per batch.

Quick Start

Run the migration planner in analyze mode on your codebase to identify breaking changes and produce an effort estimate for the source-to-target upgrade.

Frequently Asked Questions about migration-planner

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

FAQPage Schema
How do I safely upgrade a major framework version without breaking my codebase?▼

To safely upgrade a major framework version, analyze breaking changes and map impacted files/APIs to generate a dependency-aware, progressive migration plan with per-lot verification and rollback guardrails.

What is the best way to plan a major version upgrade for a backend runtime?▼

The best way to plan a major version upgrade is to classify changes as automatic, semi-automatic, or manual, then execute ordered batches with atomic commits and continuous CI verification to isolate failures.

Can I execute incremental migrations with rollback for frontend framework updates?▼

Yes, you can execute incremental migrations for frontend frameworks by applying changes lot by lot, running type and visual checks, and using atomic commits to ensure safe rollback if a batch fails.

How do I estimate the effort required to resolve breaking changes in a web toolchain?▼

To estimate the effort for resolving breaking changes, scan the project to identify impacted imports and APIs, classify the required change types, and produce an overall effort estimate for the upgrade.

When should I use a progressive migration plan instead of a big-bang upgrade?▼

Use a progressive migration plan instead of a big-bang upgrade when incremental change is required, allowing you to order dependency-aware batches, verify builds continuously, and maintain a rollback strategy.

Related Skills

Explore More Software Engineering Skills→
NotysotyNotysoty
9

Migration Guide Writer

Generate structured migration guides for breaking API changes.

Community
Advanced
13g789512313g7895123

feature-f3-position-sizing

Convert per-trade investment amounts into integer lot quantities using limit-up pricing.

Community
Intermediate
AndyHsuTWAndyHsuTW

django-verification

Automate Django project verification with linters, security scanners, and tests.

Community
Advanced
dhruvinrsonidhruvinrsoni

legacy-upgrade

Plan and execute framework or runtime upgrades with codemods and rollback validation.

Community
Advanced