migrate-nanocrew

Extract fork customizations into a migration guide and reapply them on upstream.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CjLogic/nanocrew --skill migrate-nanocrew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-nanocrew
Source: https://github.com/CjLogic/nanocrew/tree/main/.codex/skills/migrate-nanoclaw
Command: npx skills add https://github.com/CjLogic/nanocrew --skill migrate-nanocrew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts user customizations from forks, 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 that captures both the intent and the implementation details.
  • Upgrades upstream by checking out clean upstream in a worktree, then reapplying customizations using the guide.
  • No-merge upgrades with rollback safety and deterministic application across forks.

Quick Start

Run migrate-nanocrew to generate a migration guide from your fork and prepare for a clean upgrade.

Frequently Asked Questions about migrate-nanocrew

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?

Fork migration involves extracting customizations into a replayable guide and reapplying them on a clean upstream base. This intent-based approach replaces traditional merges, ensuring deterministic application across config, code, and personas.

What is intent-based migration for git forks?

Intent-based migration captures customization intent and implementation details in a replayable guide. It upgrades upstream by applying this guide to a clean worktree, avoiding merge conflicts and enabling deterministic, conflict-free upgrades.

How do I generate a migration guide from a fork before upgrading?

Run the migration tool on your fork to extract customizations into a structured guide capturing intent and implementation details. This prepares changes for deterministic reapplication on a clean upstream base.

Can I rollback a fork upgrade if the migration fails?

The migration process includes rollback safeguards and base/revision tracking. If reapplying customizations fails, you can safely revert the worktree to its previous state.

Does merge-based upgrade work for custom configs and personas?

Merge-based upgrades often conflict with custom configs, code, and personas. Intent-based migration extracts these customizations into a guide and reapplies them deterministically on a clean upstream worktree, bypassing merge issues entirely.

What are the limitations of intent-based fork migration?

Intent-based migration relies on accurately extracting customizations; heavily entangled or undocumented changes may be difficult to capture. It requires checking out a clean upstream worktree, meaning local uncommitted work must be stabilized beforehand.