migrate-nanoclaw

Name: migrate-nanoclaw
Availability: InStock
Author: jboothomas

Extract fork customizations into a migration guide for clean upstream checkouts.

1|2|Updated Apr 8, 2026

Search Tags:#automation #git #migration #worktree #upstream #customizations

Ready to run

npx skills add https://github.com/jboothomas/nauggieclaw --skill migrate-nanoclaw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-nanoclaw
Source: https://github.com/jboothomas/nauggieclaw/tree/main/.claude/skills/migrate-nanoclaw
Command: npx skills add https://github.com/jboothomas/nauggieclaw --skill migrate-nanoclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures every fork-specific customization and turns it into a replayable migration guide so you can skip painful git merges and apply the same intent-driven changes on a fresh upstream checkout.

Core Features & Use Cases

Migration guide creation: Extracts intent, implementation details, and relevant code snippets so future sessions can reproduce your custom configs, personas, and scripts without guessing.
Safe upgrade workflow: Spins up worktrees, reapplies upstream skill branches, and reintroduces your customizations in a validated order while keeping backups, diagnostics, and safety gates intact.
Use Case: When NauggieClaw upstream refactors src/ or skill merges conflict with your tweaks, this Skill documents what you changed and replays it in a clean environment.

Quick Start

Invoke migrate-nanoclaw via Auggie to build the migration guide and replay your customizations on the latest upstream commit.

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 forked git repository without merge conflicts?▼

To avoid merge conflicts when upgrading a fork, extract your customizations into a replayable migration guide and reapply them on a clean upstream checkout. This intent-based approach documents your changes and replays them in a validated order instead of merging branches.

What is an intent-based migration guide for upstream updates?▼

An intent-based migration guide captures the reasoning, implementation details, and code snippets behind your fork customizations. It allows future sessions to reproduce your personalized configs, personas, and scripts on a fresh upstream checkout without guessing.

How do I reapply custom code to a clean upstream checkout?▼

You reapply custom code to a clean upstream checkout by spinning up git worktrees and reintroducing your customizations in a validated order. The process keeps backups and diagnostics intact while replaying your documented intent.

Does this migration workflow support git worktrees and backups?▼

Yes, this migration workflow supports git worktrees and backups. It spins up worktrees to test upgrades safely, reapplies upstream skill branches, and maintains safety gates and diagnostics throughout the reapplication process.

What is the best way to preserve custom skills during an upstream refactor?▼

The best way to preserve custom skills during an upstream refactor is to extract their intent and implementation into a migration guide. You can then safely reintroduce your personalized skills and custom code onto the latest upstream commit in a clean environment.

Why do I need a migration guide instead of using standard git merges?▼

You need a migration guide instead of standard git merges because upstream refactors often conflict with local tweaks. A migration guide captures intent and replays customizations on a clean checkout, avoiding painful merge conflicts and ensuring validated reapplication.