update-nanoclaw

Integrate upstream NanoClaw updates while preserving local modifications via Git operations.

10|16|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/qwibitai/nanoclaw-whatsapp --skill update-nanoclaw-qwibitai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-nanoclaw
Source: https://github.com/qwibitai/nanoclaw-whatsapp/tree/main/.claude/skills/update-nanoclaw
Command: npx skills add https://github.com/qwibitai/nanoclaw-whatsapp --skill update-nanoclaw-qwibitai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you safely incorporate upstream changes into your customized NanoClaw installation without losing your local modifications or wasting AI tokens.

Core Features & Use Cases

  • Safe Updates: Integrates upstream changes with a focus on preserving your customizations.
  • Conflict Resolution: Provides tools to preview and resolve merge conflicts efficiently.
  • Rollback: Creates automatic backups, allowing you to revert changes if needed.
  • Use Case: You've heavily customized your NanoClaw setup and a new version is released. Instead of a risky manual merge or a full re-setup, you use this skill to pull in the latest features and bug fixes while ensuring your custom agents and configurations remain intact.

Quick Start

Run the update-nanoclaw skill to synchronize your local NanoClaw repository with the latest upstream changes.

Frequently Asked Questions about update-nanoclaw

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

FAQPage Schema
How do I sync upstream updates to a customized git repository without losing local changes?

To sync upstream updates safely, this skill integrates changes via Git operations while preserving local modifications. It performs preflight checks, creates backups, and only opens conflicted files to minimize token usage during the merge process.

What is the best way to preview merge conflicts before updating my codebase?

Previewing merge conflicts is handled by running the skill's conflict preview feature before applying updates. It relies on Git operations to detect upstream changes and selectively cherry-pick updates, allowing you to review conflicts before committing.

How do I cherry-pick upstream commits into a heavily customized installation?

You can cherry-pick upstream commits by utilizing the skill's selective cherry-picking strategy. It safely integrates specific upstream changes into your customized installation, ensuring your custom agents and configurations remain intact.

Can I validate my codebase after merging upstream changes using npm?

Yes, validation is performed via npm build and test commands after integrating upstream changes. The skill automatically runs these checks to ensure your customized installation remains stable and functional following the merge.

What happens if a breaking change is detected during a git rebase?

When breaking changes are detected during a merge or rebase, the skill automatically invokes an automated migration skill to handle the transition. It also creates automatic backups beforehand, allowing you to revert if needed.

Does this update tool support rollback for customized local git repositories?

Yes, the tool supports rollback by creating automatic backups before integrating upstream changes. If the sync fails or conflicts become unmanageable, you can safely revert your customized installation to its previous state.