update

Fetch and merge upstream NanoClaw changes while preserving local customizations.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/webboty/flexclaw --skill update-webboty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/webboty/flexclaw/tree/main/.claude/skills/update
Command: npx skills add https://github.com/webboty/flexclaw --skill update-webboty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Keeps a NanoClaw installation synchronized with upstream changes while preserving user customizations, installed skills, and local patches, reducing the risk of lost work or broken builds after updates.

Core Features & Use Cases

  • Fetch & Extract Upstream: Adds or uses an upstream remote, fetches main, and extracts only tracked paths into a temporary directory.
  • Preview & Review: Runs a preview that reports files changed, files deleted, conflict risk, and custom patches at risk so users can decide before applying.
  • Apply & Recover: Applies updates via TypeScript update scripts, re-applies custom patches and skills, runs migrations, resolves merge conflicts using intent files and user confirmation, and verifies changes with build and test steps.
  • Use Case: Ideal for users who maintain a fork of NanoClaw and want a guided, reversible process to pull upstream changes without losing skill-based customizations.

Quick Start

Ask the assistant to run the update skill to fetch upstream changes, preview diffs, resolve conflicts interactively, reapply custom skills, run migrations, and verify builds and tests.

Frequently Asked Questions about update

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

FAQPage Schema
How do I merge upstream changes into a forked repository without losing local customizations?

To merge upstream changes without losing local customizations, you need a process that extracts tracked paths, previews diffs, re-applies custom patches, and resolves conflicts using intent files. This ensures local skills are preserved during the update.

What is the best way to preview diffs and conflict risks before applying upstream updates?

Previewing upstream updates involves running a script that fetches main, extracts changes into a temporary directory, and reports files changed, files deleted, and custom patches at risk. This helps you decide whether to apply the update safely.

How do I resolve merge conflicts interactively when syncing a forked project?

Resolving merge conflicts interactively involves using intent files and user confirmation to guide the resolution process. This ensures that conflicts are resolved according to your specific customizations and project requirements.

Can I run npm build and test verification automatically after applying upstream updates?

Yes, you can run npm build and test verification automatically after applying upstream updates. This validates that the merged changes and re-applied custom skills do not break existing functionality.

Does updating a forked NanoClaw project support running TypeScript migration scripts?

Yes, updating a forked NanoClaw project supports running TypeScript update and migration scripts. This allows you to sync core code and run necessary migrations while preserving local patches and installed skills.