update-nanoclaw

Integrate upstream NanoClaw changes into customized installs with backups and rollback.

Updated Jan 19, 2026

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

Ready to run

npx skills add https://github.com/clsandoval/monorepo --skill update-nanoclaw-clsandoval

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrate upstream NanoClaw changes into a customized install while preserving local modifications and minimizing disruption.

Core Features & Use Cases

Preflight checks ensure a clean working tree and detect upstream remotes.
Backup creates a timestamped backup branch and tag to enable rollback.
Preview shows upstream commits and local drift, plus file-level impact.
Update paths support merge, cherry-pick, or rebase with configurable behavior.
Conflict handling guides safe resolution of conflicts without refactoring.
Validation runs build and tests to verify integrity after the update.
Rollback provides a straightforward revert path to the backup point.
Token efficiency minimizes token usage by focusing on conflicted areas.

Quick Start

Run the update-nanoclaw command in Claude Code to begin incorporating 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 safely merge upstream changes into a customized NanoClaw install?▼

Safely merge upstream changes by running preflight checks, creating timestamped backup branches, previewing file-level impact, and validating builds. This workflow preserves local modifications while integrating upstream updates through configurable merge, cherry-pick, or rebase paths.

Can I roll back a failed NanoClaw update if conflicts break my deployment?▼

Yes, you can roll back a failed NanoClaw update using the deterministic backup branch and tag created during preflight. This provides a straightforward revert path to restore your customized install to its previous working state.

What is the best way to preview upstream commits before updating a forked NanoClaw deployment?▼

Preview upstream commits and local drift before updating a forked NanoClaw deployment by using the skill's preview feature. It shows incoming commits, local modifications, and file-level impact to help you assess breaking changes before integration.

Does the NanoClaw update process support cherry-picking specific commits instead of a full merge?▼

Yes, the NanoClaw update process supports cherry-picking specific upstream commits instead of performing a full merge. You can choose between merge, cherry-pick, or rebase update paths to control how upstream changes integrate into your customized deployment.

How are merge conflicts handled when integrating upstream NanoClaw changes?▼

Merge conflicts are handled by guiding safe resolution focused on conflicted areas to minimize token usage. The workflow avoids refactoring during conflict resolution and runs build and test validation afterward to verify integrity.

Do I need a clean working tree before incorporating upstream NanoClaw updates?▼

Yes, you need a clean working tree before incorporating upstream NanoClaw updates. Preflight checks enforce this requirement and detect upstream remotes to ensure your customized install is in a safe state before the backup and integration process begins.