code-migration

Automate code migrations to canonical locations with validation scripts.

3|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/xiaden/nomarr --skill code-migration-xiaden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-migration
Source: https://github.com/xiaden/nomarr/tree/main/.github/skills/code-migration
Command: npx skills add https://github.com/xiaden/nomarr --skill code-migration-xiaden

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a governance framework to ensure clean, complete migrations of logic between code layers, preventing half-migrations and ensuring canonical ownership.

Core Features & Use Cases

  • Migration planning and ownership rules to ensure a single canonical owner for each responsibility.
  • A concrete migration checklist that guides moving code, updating call sites, banning deprecated patterns, and deleting legacy implementations.
  • Enforced workflows and tooling references to validate removals and keep references up to date across the codebase.

Quick Start

Review a migration task, move the implementation to its canonical location, update all call sites, delete the old code, and run the automated validation steps.

Frequently Asked Questions about code-migration

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

FAQPage Schema
How do I formalize code migrations to prevent half-migrations and stale references?

To formalize code migrations, use a governance framework that enforces canonical ownership and a concrete checklist. This guides moving implementations, updating call sites, and deleting legacy code to prevent half-migrations and stale references.

What is canonical ownership in the context of refactoring and deprecating code?

Canonical ownership ensures a single, authoritative location for each code responsibility during refactors. It provides migration planning rules to guide moving code across modules and services, ensuring clean deprecations and architecture changes without duplication.

How do I validate code removal and update call sites when moving logic between libraries?

Validate code removal by applying enforced workflows, Ruff rules, and validation scripts. These tools detect stale references and ensure all call sites are updated when moving logic between libraries, confirming the migration is complete.

What's the best way to automate a code migration checklist across modules and services?

The best way to automate a code migration checklist is to enforce consistent guidelines and tooling references. This automates moving implementations to canonical locations, updating references, banning deprecated patterns, and deleting legacy code.

Do I need Ruff rules and validation scripts to ensure migrations complete successfully?

Yes, you need consistent guidelines, Ruff rules, and validation scripts to ensure migrations complete successfully. These enforced tooling references are required to validate removals, detect stale references, and keep references updated across the codebase.