update-nanoclaw

Merge upstream NanoClaw updates into customized installs with git workflows.

5|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill update-nanoclaw-chiptoe-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-nanoclaw
Source: https://github.com/chiptoe-svg/nanoclaw_gccourse/tree/main/.claude/skills/update-nanoclaw
Command: npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill update-nanoclaw-chiptoe-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you customize your NanoClaw fork for your classroom or use case, pulling upstream updates risks overwriting your custom settings, skills, or channel integrations, or forcing a full reinstall that wastes time and risks configuration loss.

Core Features & Use Cases

  • Pre-update preview: See exactly what upstream changes include before applying them, grouped by impact area (skills, source code, container, build config).
  • Flexible update paths: Choose to merge all changes, cherry-pick specific commits, or rebase for linear history, with automatic conflict previews before any changes are made.
  • Built-in safety guardrails: Automatic timestamped backups let you roll back instantly if something goes wrong, and breaking change detection alerts you to required migration steps.
  • Low token usage: Only opens files with actual conflicts, using git commands for all other checks to avoid unnecessary context bloat. Use case: For instructors running customized NanoClaw classrooms, this lets you incorporate upstream security patches and new features without reconfiguring your custom TA personas, course-specific skills, or pre-set channel integrations.

Quick Start

Use the update-nanoclaw skill to pull the latest upstream NanoClaw changes into your customized install while preserving all your custom settings.

Frequently Asked Questions about update-nanoclaw

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

FAQPage Schema
How do I pull upstream updates into a customized git fork without overwriting my changes?

To pull upstream updates without losing customizations, use git-native merge, cherry-pick, or rebase workflows that preview conflicts before applying them. This syncs your fork safely while preserving local modifications and avoiding full reinstalls.

What is the safest way to sync a forked repository with upstream releases?

The safest way to sync a forked repository with upstream releases involves creating automatic timestamped backups before applying changes. This enables instant rollback if conflicts occur, ensuring your custom configurations remain intact during synchronization.

How do I cherry-pick specific commits from an upstream repository into my custom fork?

You can cherry-pick specific upstream commits by selecting a flexible update path that targets only the changes you need. This process includes automatic conflict previews to show exactly what will change before any modifications are applied.

Can I preview breaking changes before merging upstream updates into my local git repository?

Yes, you can preview breaking changes before merging upstream updates by running a pre-update analysis grouped by impact area. This detection alerts you to required migration steps and shows exactly what upstream changes include before you apply them.

How do I update a self-hosted deployment without triggering a full reinstall?

You can update a self-hosted deployment without a full reinstall by incorporating upstream updates through targeted git workflows. This approach opens only files with actual conflicts, reducing manual effort and avoiding unnecessary context bloat.