update-nanoclaw

Merges upstream NanoClaw changes into customized forks with backup, conflict preview, and validation.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill update-nanoclaw-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-nanoclaw
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/update-nanoclaw
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill update-nanoclaw-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customized NanoClaw installs drift from upstream over time, and manually merging updates risks losing local modifications, hitting unexpected conflicts, or missing breaking changes that require migration steps. ## Core Features & Use Cases - Safe Update Workflow: Creates timestamped backup branches and tags before touching anything, previews upstream changes grouped by area (skills, host source, container, build config), and offers merge, cherry-pick, rebase, or abort paths. - Conflict Preview and Resolution: Runs a dry-run merge to list conflicting files before committing, then resolves only conflict markers while preserving local customizations. - Validation and Breaking Changes Handling: Runs builds, tests, and container rebuilds as needed, parses CHANGELOG.md for new [BREAKING] entries, and offers to run the referenced migration skills. - Use Case: You forked NanoClaw months ago and added custom channels. Run the skill to preview 40 upstream commits, cherry-pick the fixes you want, resolve two conflicts, and get rollback instructions with a backup tag. ## Quick Start Ask Claude Code to run /update-nanoclaw to preview and apply upstream NanoClaw changes to your customized install.

Frequently Asked Questions about update-nanoclaw

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

FAQPage Schema
How do I update a customized NanoClaw fork from upstream?

Run /update-nanoclaw in Claude Code. It fetches the upstream remote, creates a backup branch and tag, previews changes grouped by area, and lets you merge, cherry-pick, or rebase before validating with builds and tests.

How to cherry-pick specific upstream commits instead of merging everything?

Choose the selective update path when prompted. The skill lists upstream commits since your merge base, asks which hashes you want, and applies them with git cherry-pick, resolving only conflict markers if conflicts occur.

Can I preview merge conflicts before applying an upstream update?

Yes. The skill runs a dry-run merge with git merge --no-commit --no-ff, lists conflicting files, then aborts the dry-run so you can decide whether to proceed before anything is committed.

How do I roll back if the NanoClaw update breaks something?

Every run creates a backup tag and branch named pre-update-<hash>-<timestamp>. Roll back with git reset --hard <backup-tag>, which restores your exact pre-update state.

What happens when an update introduces breaking changes?

After validation, the skill diffs CHANGELOG.md against the backup tag and looks for [BREAKING] entries. Each one is shown to you, and you can choose to run the referenced migration skills immediately or handle them manually.

Why does the update skill refuse to run with uncommitted changes?

It requires a clean working tree, checked via git status --porcelain, so merges and conflict resolution never mix with uncommitted work. Commit or stash first; the only exception is the skill's own self-refresh from upstream.