update

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The NanoClawbster update skill streamlines keeping your installation current by fetching upstream changes, merging them with your local customizations, and applying needed migrations in a controlled flow that preserves user work.

Core Features & Use Cases

  • Automated fetch and merge of upstream changes with local customizations.
  • Pre-flight validation, conflict visibility, and guided resolution during upgrades.
  • Migration execution, build and test verification, and final status reporting.

Quick Start

Run the update workflow to fetch upstream changes, preview the changes, and apply migrations.

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 with local customizations without losing my configurations?

To merge upstream changes with local customizations safely, the update workflow fetches the latest code, identifies conflicts, and applies a guided merge to preserve your configurations. Pre-flight validation ensures local modifications remain intact during the process.

What happens when an upstream merge causes conflicts during an upgrade?

When an upstream merge causes conflicts, the update process provides conflict visibility and guided resolution steps. This controlled flow prevents data loss by highlighting risk areas before changes are applied to your customized installation.

Can I preview changes before running migrations on a customized installation?

Yes, you can preview changes before running migrations. The update workflow generates an upgrade preview showing exactly what will be modified, allowing you to assess conflict risk and verify build status before applying anything.

Does the update process verify builds and run tests after applying migrations?

The update process does verify builds and run tests after applying migrations. Once upstream changes are merged and migrations are executed, the system reports build and test results to confirm the installation remains stable.

When do I need to run migrations after fetching upstream changes?

You need to run migrations after fetching upstream changes whenever the core system updates require structural data or configuration modifications. The update workflow automates this by executing migrations immediately after the merge completes.

What are the limitations of automating upstream merges for heavily customized configurations?

A limitation of automating upstream merges for heavily customized configurations is the potential for unresolved conflict risks. While the workflow provides guided resolution, complex structural changes may still require manual intervention to ensure stability.