update

Fetch upstream NanoClaw changes, merge local customizations, and run migrations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, git, tar, and includes scripts (resource) components.

What problem does it solve?

This Skill automates updating a NanoClaw installation by fetching upstream repository changes, merging them with local customizations and skills, and running required migrations and verification steps so users avoid manual, error-prone merges.

Core Features & Use Cases

  • Automated Fetch & Archive: Detects or adds an upstream remote, fetches the main branch, and extracts only the tracked paths into a temporary directory.
  • Preview and Risk Assessment: Runs a preview to enumerate files changed, deleted, conflict risks, and custom patches at risk so users can make an informed decision.
  • Safe Apply with Conflict Resolution: Applies updates, attempts to reapply custom patches and skills, provides guided conflict resolution using skill intent files, runs migrations, builds and tests, and cleans up temporary artifacts.
  • Use Case: Keep a forked NanoClaw repository up to date while preserving community skills and local modifications without losing work or breaking builds.

Quick Start

Use the update skill to fetch upstream changes, preview differences, and apply the update while preserving skills and customizations.

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 git repository without losing local customizations?

To merge upstream changes safely, the update skill fetches the main branch, archives tracked paths, and previews file diffs and conflict risks before applying updates. It attempts to reapply custom patches and resolves merge conflicts using intent files.

What is the best way to run database migrations and verify builds after a git merge?

The best way to run migrations and verify builds post-merge is to automate the sequence. This skill runs migration scripts immediately after applying updates, then validates the installation by executing build and test commands to ensure stability.

Can I preview git merge conflicts before applying upstream updates to my local fork?

Yes, you can preview merge conflicts before applying upstream updates. The skill performs a risk assessment that enumerates changed files, deletions, and custom patches at risk, allowing you to make an informed decision prior to execution.

Do I need node and tar installed to automate pulling upstream changes for NanoClaw?

Yes, you need node, git, and tar installed. These dependencies are required to fetch the upstream repository, extract tracked paths into a temporary directory, run migration scripts, and execute the build and test verification steps.

How does conflict resolution work when updating a forked NanoClaw repository?

Conflict resolution when updating a NanoClaw fork uses skill intent files to guide the process. If conflicts occur during the merge, the skill references these intent files to safely reconcile upstream changes with your local modifications.

Why does my local build break after merging upstream changes and how can I prevent it?

Builds often break after merging upstream changes due to unresolved conflicts or skipped migrations. This skill prevents breakage by running required migration scripts, backing up state, and verifying the final build and tests before completing the update.