/migrate

name: migrate
description: Migrate from npm-installed metaswarm to the marketplace plugin — removes redundant files with safety checks

Migration Skill

Migrate a project from npm-installed metaswarm (`npx metaswarm init`) to the marketplace plugin. Removes redundant embedded files with a safety protocol that prevents data loss.

**When to use**: The SessionStart hook detects `.claude/plugins/metaswarm/.claude-plugin/plugin.json` (legacy embedded plugin) and recommends running this skill.

---

IMPORTANT: Safety & Messaging Guidelines

**The user MUST understand this before any file list is shown:**

Before presenting any migration preview or file list, ALWAYS lead with this framing:

> **What this migration does**: The marketplace plugin now provides all the skills, commands, rubrics, and guides that were previously copied into your project directory. This migration simply removes those redundant copies — the originals now live in the plugin itself. > > **Nothing is lost**: Your project-specific files (CLAUDE.md, .coverage-thresholds.json, .beads/, bin/, scripts/) are NEVER touched. Only duplicate metaswarm framework files are removed. > > **Fully reversible**: All removals are staged with `git rm` (not permanently deleted). Before you commit: > - Undo everything: `git restore --staged . && git checkout -- .` > - After committing: `git revert HEAD` > > **No commit is made automatically** — you review and commit when you're satisfied.

**Tone**: Be reassuring, not alarming. Say "cleaning up XX redundant copies" not "deleting XX files". Say "these files now live in the plugin" not "these files will be removed". Frame the migration as housekeeping, not destruction.

**When showing file counts**: If there are many files (e.g., 40+), explain that the large count is because the old npm installer copied the entire plugin framework into `.claude/plugins/metaswarm/` — that one directory accounts for most of the count, and it's all framework code that's now served directly by the plugin.

---

Step 1: Pre-flight Check

1. Confirm this skill is running from the marketplace plugin (if this skill loaded, the plugin is active) 2. Read `.metaswarm/project-profile.json` -- if `"distribution": "plugin"` is already set, inform the user migration was already completed and exit 3. Verify `.claude/plugins/metaswarm/.claude-plugin/plugin.json` exists -- if not, there is nothing to migrate; inform the user and exit

If the plugin is not loaded, the user needs to install it first: `/plugin marketplace add dsifry/metaswarm-marketplace`

---

Step 2: Inventory Legacy Files

Scan for files installed by `npx metaswarm init` that are now provided by the marketplace plugin.

**Candidates for removal:**

| Category | Path pattern | |---|---| | Embedded plugin | `.claude/plugins/metaswarm/` (entire directory) | | Rubrics | `.claude/rubrics/*.md` | | Guides | `.claude/guides/*.md` | | Old commands | `.claude/commands/metaswarm-setup.md`, `.claude/commands/metaswarm-update-version.md` |

**NEVER removed** (project-local files): `CLAUDE.md`, `.coverage-thresholds.json`, `.metaswarm/project-profile.json`, `.beads/`, `bin/`, `scripts/`, `.github/workflows/`, `.claude/commands/` shims.

---

Step 3: Content Verification

For each removal candidate, verify it is an unmodified metaswarm file using SHA-256 hash comparison.

**Hash protocol:** 1. Read file content 2. Normalize line endings to LF (`\r\n` -> `\n`, `\r` -> `\n`) 3. Strip trailing whitespace from each line 4. Strip trailing newlines 5. Compute SHA-256 of normalized content 6. Compare against hash of the corresponding file from the marketplace plugin's own directories (rubrics/, guides/, etc.)

Computing hashes from the plugin's live files ensures the hash list stays current -- no hardcoded hashes that drift.

**Classification:**

| Result | Action | |---|---| | Hash matches | **Unmodified** -- add to deletion list | | Hash differs | **User-modified** -- flag for user decision, never auto-delete | | Not in hash list | **Unknown file** -- skip entirely |

---

Step 4: Dry Run Preview

Display the complete migration plan before any changes. **Lead with the safety framing from the guidelines above**, then show the preview:

## Migration Preview

These are redundant copies of framework files that are now provided by the plugin.
All removals are staged (not committed) — you can undo everything before committing.

### Redundant framework files to clean up (XX files)
These are unmodified copies that the plugin now provides directly:
- .claude/plugins/metaswarm/ (embedded plugin copy — XX files, now served by marketplace plugin)
- .claude/rubrics/<each matching file> (now in plugin's rubrics/)
- .claude/guides/<each matching file> (now in plugin's guides/)
- .claude/commands/metaswarm-setup.md (replaced by plugin command)
- .claude/commands/metaswarm-update-version.md (replaced by plugin command)

### Files you've customized (require your decision)
- .claude/rubrics/code-review-rubric.md (MODIFIED — your changes are preserved until you decide)

### Your project files (NEVER touched)
- CLAUDE.md, .coverage-thresholds.json, .metaswarm/, .beads/, bin/, scripts/

### What gets added
- 6 command shims in .claude/commands/ (thin wrappers that route to plugin commands)
- .metaswarm/project-profile.json updated with "distribution": "plugin"

### How to undo (before committing)
git restore --staged . && git checkout -- .

---

Step 5: User Confirmation

Use `AskUserQuestion`:

• Remind the user: "This stages the cleanup — nothing is committed yet. You can undo with `git restore --staged . && git checkout -- .`"
• Ask: "Ready to clean up the redundant framework files?" (not "Ready to delete files?")
• For each user-modified file, ask individually: keep, remove, or show diff
• If the user chooses "diff", display the difference between their version and the plugin's, then re-ask

---

Step 6: Git Safety

Before executing removals: 1. Run `git statu