update-nanoclaw

Integrate upstream NanoClaw updates into customized git forks with rollback-ready changes.

Updated May 7, 2026

Search Tags:#git #rollback #merge #update #cherry-pick #upstream #nanoclaw

Ready to run

npx skills add https://github.com/Bartunek/nanoclaw --skill update-nanoclaw-bartunek

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NanoClaw forks drift from upstream as you customize them. This skill provides a safe, rollback-ready workflow to pull upstream changes into your install without losing local modifications.

Core Features & Use Cases

Preflight checks, backups, and multiple update strategies (merge, cherry-pick, rebase) to minimize disruption.
Upstream change previews, deterministic conflict handling, and easy rollback if needed.
Validation steps, including build and test checks, plus optional breaking-change detection to ensure stability.

Quick Start

Run the /update-nanoclaw command in Claude Code to begin syncing upstream changes and applying your customizations.

Frequently Asked Questions about update-nanoclaw

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

FAQPage Schema

How do I merge upstream changes into a customized git fork without losing local modifications?▼

To merge upstream changes safely, you need a workflow that creates backups, establishes a rollback point, and uses strategies like merge, cherry-pick, or rebase to resolve conflicts while preserving local customizations. It validates builds and tests before finalizing.

What is the best way to sync a drifted fork with upstream using minimal tokens?▼

The best way to sync a drifted fork is using a low token usage update strategy that previews upstream changes, handles conflicts deterministically, and provides an easy rollback if the integration fails build or test checks.

How do I rollback a failed upstream merge in a git repository?▼

To rollback a failed merge, the update process creates a preflight backup and a rollback point before applying changes. If build or test validation fails after integrating upstream updates, you can revert to the previous state.

Do I need a git upstream remote configured to sync fork updates?▼

Yes, you need a git repository with an upstream remote configured. The update process requires this setup to fetch upstream changes, preview them, and apply updates through merge, cherry-pick, or rebase while keeping token usage low.

How can I detect breaking changes when pulling upstream updates into a customized install?▼

Breaking change detection is an optional validation step during the update process. After applying upstream changes via your chosen strategy, the workflow validates builds and runs tests to ensure stability before finalizing the integration.