migrate

The migrate skill safely removes redundant metaswarm framework files by verifying SHA-256 content against the marketplace plugin, staging git rm operations for unmodified copies, and creating command shims while preserving project-specific data.

The best way to migrate an npx metaswarm project is running this skill, which performs pre-flight checks, inventories embedded files, compares SHA-256 normalized contents, stages git rm removals, and creates command shims routing to the marketplace plugin.

Yes, the migration process verifies file contents by comparing SHA-256 normalized hashes against the marketplace plugin to identify unmodified framework copies for safe removal while explicitly flagging user-modified files to prevent data loss.

Yes, you can undo the metaswarm framework migration because the skill enforces reversible git-based safeguards, staging removals with git rm and offering explicit undo instructions to safely revert the cleanup if the wrong files are targeted.

You need to run a metaswarm file cleanup when your project was initialized with npx metaswarm, contains an embedded .claude/plugins/metaswarm copy, and requires safe staging of redundant framework files for cleanup using the marketplace plugin.

The migration skill flags certain files instead of removing them when SHA-256 verification detects user modifications, ensuring project-specific data is never touched or lost during the redundant framework cleanup and plugin redirection process.