update-nanoclaw

Automates NanoClaw updates with backups and GitLab/GitHub/Gitea/Radicle integration.

Updated Mar 12, 2026

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

One-click install

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

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently bring upstream NanoClaw updates into a customized install while preserving local modifications, enabling safe and reliable maintenance.

Core Features & Use Cases

Preflight checks ensure a clean working tree before applying updates.
Automatic backups (branch and tag) provide a rollback point for safe experimentation.
Flexible update strategies (merge, cherry-pick, or rebase) with conflict previews and minimal token use.
Validation and breaking-change assessment guide downstream migrations and prevent regressions.
Clear summary of changes and rollback instructions after completion.

Quick Start

Run /update-nanoclaw in Claude Code to start safely syncing upstream NanoClaw 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 a forked repository with upstream changes without losing local modifications?▼

To sync a fork with upstream changes without losing local modifications, you can use merge, cherry-pick, or rebase strategies. This Skill coordinates preflight checks, automatic backups, and conflict previews to safely synchronize customized installs while preserving local files.

What is the best way to apply selective cherry-picks from upstream to a customized branch?▼

The best way to apply selective cherry-picks from upstream is to use a coordinated update workflow that previews conflicts first. This Skill calculates the base, previews conflicts, and validates breaking changes before applying the cherry-picked commits to your branch.

How does breaking-change assessment work when updating a customized codebase?▼

Breaking-change assessment during a customized codebase update works by validating synced commits and identifying breaking changes before finalizing. This Skill assesses upstream changes and specifies migration workflows via breaking-change-driven skills to prevent regressions.

Can I safely rebase a diverged fork against upstream without losing uncommitted work?▼

You cannot safely rebase with uncommitted work, as preflight checks require a clean working tree. This Skill enforces a clean state before starting, then creates automatic branch and tag backups to provide a rollback point before applying the rebase.

When do I need to calculate a new base before merging upstream updates?▼

You need to calculate a new base before merging upstream updates when your fork has diverged from the upstream repository. This Skill specifies the required workflow for base calculation, remote setup, and conflict resolution to safely synchronize the changes.

Does updating a forked project automatically create a rollback point?▼

Yes, updating a forked project can automatically create a rollback point. This Skill generates automatic branch and tag backups during the preflight stage, providing a safe rollback mechanism before applying upstream merges, cherry-picks, or rebases.