update-nanoclaw

Automate upstream NanoClaw merges with preflight checks, backups, and rollback.

5|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/thmtz/nanoclaw-fleet --skill update-nanoclaw-thmtz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-nanoclaw
Source: https://github.com/thmtz/nanoclaw-fleet/tree/main/.claude/skills/update-nanoclaw
Command: npx skills add https://github.com/thmtz/nanoclaw-fleet --skill update-nanoclaw-thmtz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently bring upstream NanoClaw updates into a customized install without losing local changes, while minimizing token usage.

Core Features & Use Cases

  • Preflight safety checks, automatic backups, and rollback points before applying updates.
  • Merge or cherry-pick upstream changes to preserve your customizations while staying up-to-date.
  • Breaking-change awareness and optional migration steps to keep your workflow smooth.

Quick Start

Ask Claude Code to run /update-nanoclaw to safely merge upstream NanoClaw changes into your fork.

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 fork without losing local modifications?

Merge upstream changes into a customized fork by running preflight safety checks, creating automatic backups, previewing conflicts, and applying merge, cherry-pick, or rebase strategies to preserve local modifications while integrating updates safely.

What is the best way to handle breaking changes when updating a customized install from upstream?

Handle breaking changes during an upstream update by using breaking-change awareness features that detect incompatible modifications and apply optional migration steps to keep your customized install functional and up-to-date.

Can I cherry-pick specific upstream commits instead of doing a full merge?

Yes, you can cherry-pick specific upstream commits instead of a full merge to selectively integrate changes while preserving your customizations, using built-in conflict previews and rollback points to ensure safety.

How do I rollback a failed upstream integration if conflicts break my local code?

Rollback a failed upstream integration by utilizing the automatic backup and rollback points created during preflight checks, which allow you to instantly revert your customized install to its previous working state.

Does this update process work with rebase strategies or only standard merges?

The update process works with rebase strategies, standard merges, and cherry-picks, orchestrating all three approaches to safely integrate upstream changes while enforcing validation and minimizing token usage throughout the workflow.