migrate-nanoclaw

Extract NanoClaw fork customizations into a migration guide for clean upstream upgrades.

5|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill migrate-nanoclaw-chiptoe-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-nanoclaw
Source: https://github.com/chiptoe-svg/nanoclaw_gccourse/tree/main/.claude/skills/migrate-nanoclaw
Command: npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill migrate-nanoclaw-chiptoe-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NanoClaw users who fork the repository to add custom configurations, modify core source code, adjust agent personas, or install additional skills face painful, time-consuming merge conflicts when upstream releases updates, as standard git merge cannot cleanly reconcile custom changes with upstream refactors.

Core Features & Use Cases

  • Intent-Based Migration Guide Generation: Extracts all user customizations into a structured markdown guide that captures both the intended outcome and exact implementation details (code snippets, API calls, config values) needed to reproduce changes on a clean codebase.
  • Tiered Workflow Support: Adapts to migration complexity, from lightweight single-command updates for small changes to full multi-phase migration with sub-agent exploration for heavily customized forks.
  • Safe, Isolated Upgrade Process: Uses git worktrees to validate changes on a separate branch before affecting the live install, with automatic backup tags and rollback points to prevent data loss.
  • Use Case: A classroom administrator who customized their NanoClaw fork with custom Telegram integrations, modified student role permissions, and added a custom grading skill can upgrade to the latest upstream version in minutes without manually resolving dozens of merge conflicts.

Quick Start

Use the migrate-nanoclaw skill to extract your NanoClaw fork customizations into a migration guide and upgrade to the latest upstream version without any merge conflicts.

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 customized git fork without getting merge conflicts?

To upgrade a customized git fork without merge conflicts, extract your customizations into a structured migration guide capturing intent and implementation details, then reapply those changes onto a clean upstream codebase. This deterministic approach bypasses standard git merge friction entirely.

What is intent-based migration for upgrading customized codebases?

Intent-based migration extracts user customizations into a structured markdown guide that captures both the intended outcome and exact implementation details like code snippets and config values needed to reproduce changes on a clean upstream codebase.

Can I upgrade a heavily customized fork with modified source code and agent personas?

Yes, tiered workflow support adapts to migration complexity, offering full multi-phase migration with sub-agent exploration for heavily customized forks with modified core source files, configuration values, agent personas, or added custom skills.

How do I safely upgrade my codebase without losing custom configurations?

Safely upgrade your codebase using git worktrees to validate changes on a separate branch before affecting the live install. Automatic backup tags and rollback points prevent data loss during the upstream synchronization process.

What's the best way to incorporate upstream updates into a fork with custom API integrations?

Incorporate upstream updates by generating a migration guide that documents your custom API integrations, reapplying them on a clean upstream release rather than standard git merge, which cannot cleanly reconcile custom changes with upstream refactors.