migrate-nanoclaw

Extract fork customizations into a Markdown migration guide for upstream upgrades.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/wrightchin/nanoclaw-playground --skill migrate-nanoclaw-wrightchin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-nanoclaw
Source: https://github.com/wrightchin/nanoclaw-playground/tree/main/.claude/skills/migrate-nanoclaw
Command: npx skills add https://github.com/wrightchin/nanoclaw-playground --skill migrate-nanoclaw-wrightchin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts user customizations from a fork, generates a replayable migration guide, and upgrades to upstream by reapplying customizations on a clean base. Replaces merge-based upgrades with intent-based migration.

Core Features & Use Cases

  • Extracts user customizations into a migration guide capturing intent and implementation details.
  • Uses the guide to upgrade clean upstream by reapplying customizations without merge conflicts.
  • Supports two phases: Extract and Upgrade, with backups and rollback points.

Quick Start

Describe your fork's customizations to generate a replayable migration guide and upgrade to upstream cleanly.

Frequently Asked Questions about migrate-nanoclaw

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

FAQPage Schema
How do I upgrade a fork to upstream without merge conflicts?

To upgrade a fork without merge conflicts, extract customizations into a replayable migration guide and reapply them on a clean upstream base. This intent-based migration approach replaces traditional merge-based upgrades.

What is a replayable migration guide for fork upgrades?

A replayable migration guide is a Markdown-based source of truth stored under the .nanoclaw-migrations directory. It captures user customization intents and implementation details for deterministic downstream upgrades.

How do I extract user customizations from a fork before an upgrade?

You extract user customizations during the Extract phase, which generates a migration guide capturing intent and implementation details. This guide then drives deterministic upgrades using a worktree and skill-branch merges.

Can I roll back a clean base upgrade if the reapplication fails?

Yes, the migration process supports two phases, Extract and Upgrade, with built-in backups and rollback points. This ensures you can revert a clean base upgrade if reapplying customizations fails.

Does intent-based migration work better than merge-based upgrades for forks?

Intent-based migration replaces merge-based upgrades by reapplying customizations on a clean upstream base using a generated guide. This avoids the merge conflicts typical of directly merging upstream changes into a customized fork.