migrate-template

name	migrate-template
description	Use when the user asks to update their MCP App to the latest template version, sync with upstream template, pull in template changes, upgrade the template, or migrate to a newer version of the MCP App template.

Migrating to Latest Template Version

Template remote: [e-mail]:decocms/mcp-app.git. Fetch latest, analyze changes with parallel subagents, present migration plan, apply after user approval.

Workflow

1. Fetch template remote
2. Find base commit (when user forked/cloned)
3. Get changelog (base → latest)
4. Dispatch 5 analysis subagents in parallel
5. Present migration plan — wait for user approval
6. Apply changes (subagents per category)
7. Verify: bun install && bun run check && bun run ci:check && bun run build && bun test

Step 1–3: Setup & Changelog

git remote add template [e-mail]:decocms/mcp-app.git 2>/dev/null || true
git fetch template main

# Find base commit (try in order):
git merge-base HEAD template/main                # A: shared history
git log --oneline --reverse | head -5             # B: check initial commit
# C: ask user which version they started from

# Changelog:
git log --oneline <base>..template/main
git diff <base>..template/main --stat

If no common ancestor (GitHub "Use this template"), diff full template against user's code file-by-file.

Step 4: Dispatch 5 Analysis Subagents (ALL IN PARALLEL)

Each subagent compares for its file category, checks if user also modified those files, and recommends (no conflict), (both sides changed), or (user deleted/replaced). Output as markdown table.