migrate-functionality-without-redesign

Name: migrate-functionality-without-redesign
Availability: InStock
Author: Muluh

Migrate code functionality between packages while preserving existing behavior and parity.

1|Updated Aug 11, 2026

Search Tags:#pull request #refactoring #deprecation #code migration #behavior preservation #parity testing #package reorganization

Ready to run

npx skills add https://github.com/0xMuluh/package-development-skills --skill migrate-functionality-without-redesign-0xmuluh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-functionality-without-redesign
Source: https://github.com/0xMuluh/package-development-skills/tree/main/migrate-functionality-without-redesign
Command: npx skills add https://github.com/0xMuluh/package-development-skills --skill migrate-functionality-without-redesign-0xmuluh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving functionality between packages, modules, or namespaces often gets tangled with renames, redesigns, and optimizations, making changes impossible to review and verify. This Skill enforces a disciplined migration process that separates moving code from changing its behavior. ## Core Features & Use Cases - Parity-First Migration: Characterize existing behavior, port the implementation with minimal change, and prove source-destination equivalence with dedicated parity tests. - Structured Migration Statement: Requires an explicit statement of what is moving, why, what behavior is preserved, and what is explicitly out of scope. - Staged PR Sequence: Guides destination parity, source delegation or deprecation, later redesign, and eventual removal as separate reviewable changes. - Use Case: When moving a statistical method from one R package to another, use this Skill to port the existing algorithm and result representation first, add parity tests comparing both implementations, and defer any rename or optimization to a follow-up PR. ## Quick Start Ask the AI to migrate a specific function from its current package to a new destination package while preserving its existing behavior and adding parity tests.

Frequently Asked Questions about migrate-functionality-without-redesign

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

FAQPage Schema

What are the risks of combining migration with refactoring?▼

Combining moves with renames, algorithm changes, or new result classes makes the change unreviewable as a parity check and hides semantic changes. Keep refactoring minimal and defer improvements to separate changes.