migrate-nanoclaw

Name: migrate-nanoclaw
Availability: InStock
Author: NanoCo

Extract and reapply user customizations during NanoClaw upgrades.

30.5k|12.9k|Updated Jan 31, 2026

Search Tags:#automation #git #migration #upgrade #customizations

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of upgrading NanoClaw forks with user customizations by extracting modifications into a replayable guide, preventing conflicts during upstream updates.

Core Features & Use Cases

Extract User Customizations: Generates detailed migration guides capturing intent and implementation details.
Automate Upgrades: Applies customized changes to clean upstream code, reducing manual merge conflicts.
Use Case: A developer forks NanoClaw and customizes configurations; upon upstream update, this Skill creates a guide allowing seamless reapplication of these customizations without merge conflicts.

Quick Start

Use the migration skill to extract your NanoClaw customizations into a guide that can be reused for upgrading clean upstream repositories.

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 repository without losing custom configurations?▼

To upgrade a forked repository without losing custom configurations, extract your user modifications into a replayable migration guide and reapply them to a clean upstream update. This prevents manual merge conflicts by documenting intent and implementation details.

What is the best way to automate Git migration for custom fork upgrades?▼

Automating Git migration for custom fork upgrades involves analyzing the filesystem to extract and document user modifications, then applying these customized changes to clean upstream code. This approach streamlines upgradability by generating a comprehensive, replayable migration guide.

Why does merging upstream updates into my customized fork cause conflicts?▼

Merging upstream updates into a customized fork causes conflicts because direct branch merges mix your local modifications with new base code. Extracting customizations into a standalone migration guide avoids this by cleanly reapplying changes to updated upstream repositories.

Can I extract and document code customizations before pulling upstream changes?▼

Yes, you can extract and document code customizations before pulling upstream changes by analyzing your filesystem and Git history. This generates a detailed guide capturing your modification intent, enabling conflict-free updates when you upgrade the clean base.

When should I not use a direct merge for upgrading my customized fork?▼

You should not use a direct merge for upgrading a customized fork when your local modifications are complex and deeply integrated. In these cases, applying a generated migration guide to clean upstream code reduces the risk of unresolvable merge conflicts.