update-nanoclaw

Synchronize upstream NanoClaw updates into customized installs while preserving local changes.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Arno37/nanoclaw_test --skill update-nanoclaw-arno37
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-nanoclaw
Source: https://github.com/Arno37/nanoclaw_test/tree/main/.claude/skills/update-nanoclaw
Command: npx skills add https://github.com/Arno37/nanoclaw_test --skill update-nanoclaw-arno37

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently synchronize upstream NanoClaw updates into a customized install while preserving local changes.

Core Features & Use Cases

  • Safely merge upstream changes into a customized NanoClaw fork with preflight checks and backups.
  • Preview changes and selectively apply updates via merge or cherry-pick to minimize conflicts.
  • Validate the resulting installation and surface any breaking changes for targeted migrations.

Quick Start

Run the update-nanoclaw skill to merge upstream changes into your customized NanoClaw install.

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

To merge upstream changes without losing local modifications, this Skill performs preflight safety checks and creates backups before synchronizing updates. It preserves your customized NanoClaw install by previewing changes and resolving conflicts through a guided git-based workflow.

Can I selectively cherry-pick upstream commits to minimize token usage during a NanoClaw update?

Yes, you can selectively cherry-pick upstream commits to minimize token usage. This Skill supports optional selective cherry-picks instead of full merges, allowing you to apply only the specific updates needed while reducing overall processing overhead.

What is the safest way to sync upstream git changes into a heavily modified local repository?

The safest way to sync upstream git changes is using preflight safety checks and automated backups before applying any updates. This Skill enforces safe git-based workflows, providing a guided, low-risk update process that validates the installation and surfaces breaking changes.

How do I preview breaking changes before applying upstream updates to a customized NanoClaw install?

To preview breaking changes before applying upstream updates, this Skill validates the resulting installation and surfaces any breaking changes for targeted migrations. You can preview changes first, then choose to apply updates via merge or selective cherry-pick.

Do I need a clean git working directory before synchronizing NanoClaw upstream updates?

While the metadata does not specify a clean directory as an explicit prerequisite, the Skill enforces safe git-based workflows with preflight safety checks and backups. These preflight checks are designed to ensure a low-risk update process before any synchronization begins.