migrate

Migrate npm-installed metaswarm framework files into the marketplace plugin.

Updated Apr 6, 2018
One-click install
npx skills add https://github.com/montoyaedu/Trish --skill migrate-montoyaedu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/montoyaedu/Trish/tree/main/.claude/plugins/metaswarm/skills/migrate
Command: npx skills add https://github.com/montoyaedu/Trish --skill migrate-montoyaedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate from npm-installed metaswarm to the marketplace plugin and remove redundant embedded files while safeguarding your project history and data.

Core Features & Use Cases

  • Provides a safe, reversible migration path that stages removals with git, prevents data loss, and preserves project-specific files.
  • Guides you through a dry-run preview, a user-confirmation step, and a final cleanup with clear post-migration status.
  • Applies to projects that include legacy metaswarm embedded files under .claude/plugins/metaswarm and related rubrics/guides, updating the project profile to distribution: plugin.

Quick Start

Preview the migration plan and confirm to stage the redundant framework files for removal.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I safely migrate an npm-installed framework to a marketplace plugin?

Safely migrate an npm-installed framework to a marketplace plugin using a dry-run preview, user confirmation, and staged git removals to prevent data loss and preserve project files.

What is the best way to remove duplicate embedded plugin files from a repository?

Remove duplicate embedded plugin files by staging their deletion with git, ensuring legacy files under .claude/plugins/metaswarm and related rubrics/guides are safely eliminated while updating the project profile to distribution: plugin.

Can I preview repository migrations before deleting legacy framework files?

Yes, you can preview repository migrations using a dry-run preview that outlines the removal plan for legacy embedded files before you confirm any staged git deletions.

Does the metaswarm migration process preserve project-specific files?

Yes, the metaswarm migration process preserves project-specific files by applying staged git removals only to redundant framework copies, safeguarding project history and data during the plugin transition.

When do I need to use a staged git removal for plugin migration?

Use staged git removal for plugin migration when your project contains legacy files under .claude/plugins/metaswarm and related rubrics/guides, ensuring a reversible path that prevents data loss.