update-nanoclaw

Synchronize customized NanoClaw installations with upstream changes using git-native operations.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy --skill update-nanoclaw-vincentchong123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-nanoclaw
Source: https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy/tree/main/.claude/skills/update-nanoclaw
Command: npx skills add https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy --skill update-nanoclaw-vincentchong123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of maintaining a customized NanoClaw installation by automating the process of pulling upstream changes without losing local modifications or breaking the agent environment.

Core Features & Use Cases

  • Safe Syncing: Creates automatic rollback points (branches and tags) before applying any changes to ensure your environment is always recoverable.
  • Intelligent Conflict Resolution: Previews upstream changes and conflicts, allowing you to choose between merging, cherry-picking, or rebasing.
  • Validation & Migration: Automatically runs builds, tests, and container rebuilds, while checking for breaking changes that require migration steps.

Quick Start

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

Frequently Asked Questions about update-nanoclaw

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

FAQPage Schema
How do I sync a forked git repository with upstream changes without losing local modifications?

To sync a forked git repository with upstream changes without losing local modifications, the skill creates automatic rollback points and uses git-native merge, rebase, or cherry-pick workflows to preserve your customizations.

What is the best way to handle breaking changes when pulling upstream updates for a containerized deployment?

Handling breaking changes during upstream updates involves validating system state through automated builds and dependency checks, ensuring container environment integrity while detecting if migration steps are required.

Can I preview git conflicts before merging upstream changes into my local environment?

Yes, you can preview upstream changes and conflicts before applying them, allowing you to choose between merging, cherry-picking, or rebasing to safely integrate updates into your local environment.

How do I create a rollback point before applying upstream repository updates?

Creating a rollback point before applying upstream updates is handled automatically by generating backup branches and tags, ensuring your customized installation remains recoverable if synchronization fails.

Does this upstream synchronization process validate container environment integrity after rebasing?

Yes, the upstream synchronization process validates container environment integrity by automatically running builds, tests, and container rebuilds after complex merge or rebase workflows are completed.

When should I use cherry-picking instead of merging to sync customized installations?

Cherry-picking should be used to sync customized installations when you need to selectively apply specific upstream commits rather than absorbing the entire upstream history, preserving localized modifications.