migrate-from-legacy

Automate Mycelium project migration from legacy install to plugin install.

42|3|Updated Apr 7, 2026

Search Tags:#project management #migration #tooling #code migration #mycelium

Ready to run

npx skills add https://github.com/haabe/mycelium --skill migrate-from-legacy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-from-legacy
Source: https://github.com/haabe/mycelium/tree/main/plugins/mycelium/skills/migrate-from-legacy
Command: npx skills add https://github.com/haabe/mycelium --skill migrate-from-legacy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mycelium, and includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of transitioning Mycelium projects from the legacy install format to the plugin install format, ensuring a seamless migration with minimal risk.

Core Features & Use Cases

Non-Destructive Migration: Preserves project state while removing legacy framework files.
Automatic Detection: Identifies the current install format and guides the user through the migration.
Clean Working Tree Check: Ensures the project is in a clean state before migration.
Reversible Process: Enables rollback to the original state in case of migration issues.
Use Case: If you have a Mycelium project installed in the legacy format and want to upgrade to the plugin format without losing any data or work.

Quick Start

Run the /mycelium:migrate-from-legacy command to start the migration process.

Frequently Asked Questions about migrate-from-legacy

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

FAQPage Schema

How do I migrate Mycelium projects from legacy to plugin install?▼

To migrate Mycelium projects from legacy to plugin install, run the `/mycelium:migrate-from-legacy` command. This automates the migration process, detects the current install format, and guides you through transitioning while preserving project state.

What is needed before migrating a Mycelium project to plugin form?▼

Before migrating a Mycelium project to plugin form, you need the Mycelium plugin installed and a clean working tree. The project must contain a `.claude/` directory with both canvas and skills files for the migration to proceed.

Can I rollback if the Mycelium legacy migration fails?▼

Yes, you can rollback if the Mycelium legacy migration fails because the process is reversible. It preserves project state and handles the removal of legacy framework files, enabling rollback to the original state in case of migration issues.

Does the Mycelium migration process delete my existing project files?▼

The Mycelium migration process does not delete your existing project work because it is non-destructive. It preserves project state while safely removing legacy framework files during the transition to the plugin install format.

When should I not migrate Mycelium from legacy to plugin format?▼

You should not migrate Mycelium from legacy to plugin format if your working tree is unclean. The migration requires a clean working tree to ensure a seamless transition and minimal risk of losing data or work.