What problem does it solve? Upgrading a customized NanoClaw fork with git merge produces painful conflicts because the same core files were changed on both sides. This Skill replaces merge-based upgrades with intent-based migration: it captures what you customized and why, then reapplies those changes on a clean upstream checkout. ## Core Features & Use Cases - Customization Extraction: Spawns sub-agents to diff your fork against the upstream merge-base, identifies applied skills and manual changes, and writes a structured migration guide to .nanoclaw-migrations/ with code snippets where needed. - Worktree-Based Upgrade: Checks out clean upstream in a git worktree, reapplies skills and customizations from the guide, validates with build and tests, then swaps the result into the main tree. - Safety Mechanisms: Creates backup branches and tags before touching anything, refuses to run on a dirty working tree, warns about changes made since the guide was generated, and never touches data directories like groups/, store/, or .env. - Use Case: You forked NanoClaw, changed the assistant name, added a DeepL translation step in the router, and applied the Telegram skill. When upstream ships a refactor, run this Skill to regenerate your exact setup on the new version without resolving a single merge conflict. ## Quick Start Ask the assistant to migrate my NanoClaw fork to the latest upstream version using the migrate-nanoclaw skill.
