New to Claude Skills? Learn how to install them →

Cnexu-io on GitHub

Code Migration

Free

Streamline your code migration process with a structured pipeline.

by nexu-io84.9k stars on nexu-io/open-design
1 views
Updated Aug 10, 2026
Get this skill

Free · Opens the source repo

What Code Migration does

The Code Migration skill provides a structured approach to migrating code from one framework to another, ensuring that the transition is smooth and efficient. It utilizes a default pipeline that outlines a series of stages, including code import, design extraction, token mapping, rewrite planning, patch editing, build testing, and review. This systematic flow helps developers maintain code integrity while adapting to new environments, making it suitable for projects that require careful refactoring or modernization of codebases.

At the heart of the migration process is the convergence engine, which ensures that no changes are accepted unless the build and tests pass successfully. This is crucial for maintaining quality and reliability during the migration. The pipeline is designed to repeat the verification stage until a successful build is achieved or a maximum number of iterations is reached, allowing developers to iteratively refine their code until it meets the necessary standards.

This skill is tailored for developers working on projects that involve transitioning code from one technology stack to another, such as moving from jQuery to React. It is particularly useful for teams that prioritize code quality and need a reliable method to ensure that their migrated code functions as intended. By following the defined stages, users can effectively manage the complexities of code migration without losing sight of testing and quality assurance.

In summary, the Code Migration skill is an essential tool for developers looking to modernize their codebases while ensuring that quality is not compromised. Its clear structure and emphasis on verification make it a valuable asset in any development workflow.

When to use it

Use this skill when you need to migrate code from one framework to another while ensuring build and test integrity.

When not to use it

This skill may not be suitable for simple code changes or projects that do not require a structured migration process.

What you can build with it

Migrating from jQuery to React

Use this skill to systematically transition a jQuery codebase to React, ensuring all components are tested and verified.

Updating Legacy Code

Apply this skill to refactor and modernize legacy code while maintaining functionality through rigorous testing.

Integrating New Features

Utilize the migration pipeline to integrate new features into an existing codebase, ensuring compatibility and stability.

How to install Code Migration

View source

1. Install with the skills CLI

npx skills add nexu-io/open-design/od-code-migration --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by nexu-io

od-code-migration (scenario)

Spec §1 / §10.1 / §20.3 / §21.3.2 / §23.3.3: the canonical code-migration flow. The pipeline cannot ship an accept decision without a passing build — the patch-edit ↔ build-test devloop is the convergence engine.

Default pipeline

{
  "stages": [
    { "id": "import",    "atoms": ["code-import"] },
    { "id": "tokens",    "atoms": ["design-extract", "token-map"] },
    { "id": "plan",      "atoms": ["rewrite-plan"] },
    {
      "id": "verify",
      "atoms": ["patch-edit", "build-test"],
      "repeat": true,
      "until": "(build.passing && tests.passing) || iterations>=8"
    },
    { "id": "review",    "atoms": ["diff-review"] },
    { "id": "handoff",   "atoms": ["handoff"] }
  ]
}

The scenario uses build.passing && tests.passing as the convergence signal — promoted into the spec §22.4 vocabulary by the build-test atom.

Required user inputs

A plugin built on this scenario typically declares od.inputs:

  • repoPath (string, required): pulled from od project import.
  • targetStack (form): collected by rewrite-plan.
  • testCommand / buildCommand (string, optional): overrides the inferred package.json scripts in the build-test atom.

Frequently asked questions about Code Migration

Similar skills