code-migration

Assess, plan, and execute phased codebase migrations with rollback procedures.

2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill code-migration-jlaws
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-migration
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/migration/code-migration
Command: npx skills add https://github.com/jlaws/dotfiles --skill code-migration-jlaws

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebase migrations across frameworks, languages, versions, or platforms often suffer from scope creep, hidden dependencies, and rollout risk. This skill provides structured assessment, planning templates, and rollback patterns to guide safe, predictable migrations.

Core Features & Use Cases

  • Migration Assessment: quantify scope, complexity, and risk to inform planning.
  • Strategy Selection: choose one end-to-end approach (Strangler Fig, Branch by Abstraction, Big Bang, or Parallel Run) and apply it behind a boundary.
  • Migration Plan & Rollout: draft phased execution with dependency order, milestones, and success criteria.
  • Testing & Rollback: define comparison tests, validation steps, and rollback procedures to recover from failures.
  • Automation & Artifacts: provide templates and automation approaches to reproduce migrations and future migrations.

Quick Start

Outline a phased migration for a target codebase by performing assessment, selecting a strategy, and drafting the rollout with rollback criteria.

Frequently Asked Questions about code-migration

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

FAQPage Schema
How do I safely migrate a large codebase across different tech stacks?

To safely migrate a large codebase, perform a formal assessment to quantify scope and risk, select an end-to-end strategy like Strangler Fig or Big Bang behind a boundary, and define phased rollout with rollback procedures to ensure predictable execution.

What is the best strategy for migrating complex frameworks without hidden dependency risks?

The best strategy for migrating complex frameworks involves applying an end-to-end approach such as Branch by Abstraction or Parallel Run behind a boundary, allowing you to isolate changes, manage hidden dependencies, and maintain rollback capabilities throughout the process.

How do I create a migration plan with proper rollback procedures?

Create a migration plan with proper rollback procedures by drafting phased execution with dependency order, defining milestones and success criteria, and establishing validation steps alongside rollback capabilities to recover from failures during the migration.

What testing strategy should I use when migrating codebases across versions?

Use comparison tests and validation steps as your testing strategy when migrating codebases across versions, defining specific validation criteria and rollback procedures to verify behavior and recover from any failures during the phased rollout.

When should I not use a big bang migration for my codebase?

You should not use a big bang migration when your assessment reveals high scope complexity or significant rollout risk, as alternative strategies like Strangler Fig or Branch by Abstraction provide safer boundaries and better rollback capabilities for large codebases.