skills.rest
stevengonsalvez
stevengonsalvezCOMMUNITY
Explore all skills by this author →
GitHub

migrate-nanoclaw

Extract user customizations from NanoClaw forks into a replayable migration guide.

Updated Apr 10, 2026
Search Tags:#automation#migration#upgrade#migration-guide#git-worktree#upstream#nanoclaw
One-click install
npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill migrate-nanoclaw-stevengonsalvez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-nanoclaw
Source: https://github.com/stevengonsalvez/nanoclaw-standalone/tree/main/.claude/skills/migrate-nanoclaw
Command: npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill migrate-nanoclaw-stevengonsalvez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the extraction of user customizations from a fork and generates a replayable migration guide, enabling a clean, rollback-safe upgrade to upstream without merge conflicts.

Core Features & Use Cases

  • Extract customizations into a migration guide that captures both intent and implementation details.
  • Reapply customizations on a clean upstream base using a worktree to avoid disturbing the live install.
  • Provide a deterministic upgrade path with backups, validation, and staged application of changes.

Quick Start

Describe your current environment and run migrate-nanoclaw to generate a rollback-ready migration guide.

Frequently Asked Questions about migrate-nanoclaw

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

FAQPage Schema
What is the best way to preserve customizations during an upstream NanoClaw upgrade?▼

The best way to preserve customizations during a NanoClaw upgrade is to automate the extraction of your fork's changes into a replayable migration guide. This captures config edits, source changes, and new skills to ensure a conflict-free upgrade.

How do I document custom code changes in a fork for a deterministic upgrade?▼

You document custom code changes by generating a formal migration plan that captures both the intent and precise implementation details of your customizations. This enables deterministic replay of changes on a clean upstream worktree.

Can I apply fork customizations to a clean upstream worktree without merge conflicts?▼

Yes, you can reapply customizations to a clean upstream worktree without merge conflicts by using a generated migration guide. This staged approach avoids disturbing your live install and provides a deterministic upgrade path.

Do I need a git worktree to perform a rollback-safe NanoClaw migration?▼

Using a git worktree is required to perform a rollback-safe migration because it isolates the clean upstream base. This allows you to validate staged application of customizations without disturbing your live installation.

Why does my NanoClaw fork upgrade fail when merging custom skills into upstream?▼

Fork upgrades fail when custom skills and source changes are merged directly without a migration guide. Extracting customizations first ensures recoverability and deterministic replay, avoiding conflicts on the new upstream base.

Related Skills

Explore More Software Engineering Skills→
chiptoe-svgchiptoe-svg

migrate-nanoclaw

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

Community
Advanced
SkogAISkogAI
1

sharing-skills

Guide contributors through a Git workflow to push skills upstream via PRs.

Official
Intermediate
linenoizelinenoize
1

worktree

Create, list, and clean up isolated git worktrees with safety checks.

Community
Advanced
bmsull560bmsull560

jr-rebase

Resolves git rebase conflicts in feature branches via guided marker resolution.

Community
Intermediate