migrate-NinjaClaw

Extract user customizations from a fork and generate a replayable migration guide.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/OfirGavish/NinjaClaw-Nano --skill migrate-ninjaclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-NinjaClaw
Source: https://github.com/OfirGavish/NinjaClaw-Nano/tree/main/.copilot/skills/migrate-nanoclaw
Command: npx skills add https://github.com/OfirGavish/NinjaClaw-Nano --skill migrate-ninjaclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts user customizations from a NinjaClaw fork, generates a replayable migration guide, and upgrades upstream by reapplying customizations on a clean base, replacing merge-based upgrades with intent-based migration.

Core Features & Use Cases

  • Extracts user customizations from forks and captures intent and implementation details into a migration guide.
  • Upgrades upstream by applying the guide on a clean worktree, avoiding merge-based conflicts.
  • Supports deterministic migrations, safety checks, and optional sub-agents to analyze changes across config, code, and skills.

Quick Start

Describe your fork's customizations and run the migration workflow to generate a replayable upgrade guide.

Frequently Asked Questions about migrate-NinjaClaw

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

FAQPage Schema
How do I upgrade a fork with customizations to the latest upstream without merge conflicts?

To upgrade a fork, this migration tool extracts your customizations, generates a replayable migration guide, and re-applies your changes on a clean upstream base to avoid merge conflicts.

What is intent-based migration and how does it work for custom code?

Intent-based migration captures the implementation details and purpose of your customizations into a deterministic guide, then applies that guide to a clean base instead of merging branches.

How do I generate a deterministic migration guide for my git fork?

You generate a migration guide by running the two-phase workflow, which first extracts your fork's customizations across config, code, and skills to define a verifiable upgrade plan.

Can I run preflight safety checks before applying an upstream upgrade to my custom code?

Yes, the migration workflow includes preflight safety checks and optional live testing to ensure risk-aware execution before reapplying your customizations on the clean base.

What is the best way to migrate custom configurations and skills away from a merge-based workflow?

The best way is using a two-phase Extract and Upgrade workflow, which replaces standard merge-based upgrades with an intent-based migration guide reapplying changes across config, code, and skills.

Why does my git merge fail when upgrading a heavily customized fork?

Merge-based upgrades fail due to branch conflicts, but this tool avoids the issue by extracting your customizations and applying a deterministic migration guide on a clean worktree.