skills.rest
heuuLZP
heuuLZPCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

update-nanoclaw

Integrate upstream NanoClaw updates into a customized installation via Git operations.

2|Updated Mar 4, 2026
Search Tags:#git#merge#sync#conflict resolution#update#cherry-pick#upstream
One-click install
npx skills add https://github.com/heuuLZP/nanoclaw-cn --skill update-nanoclaw-heuulzp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-nanoclaw
Source: https://github.com/heuuLZP/nanoclaw-cn/tree/main/.claude/skills/update-nanoclaw
Command: npx skills add https://github.com/heuuLZP/nanoclaw-cn --skill update-nanoclaw-heuulzp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you integrate updates from the original NanoClaw repository into your customized fork without losing your local modifications or performing a full reinstallation.

Core Features & Use Cases

  • Safe Updates: Prevents data loss by creating backups before applying changes.
  • Conflict Resolution: Guides you through resolving merge conflicts efficiently.
  • Preview Changes: Shows you exactly what upstream changes will be applied before they are merged.
  • Use Case: You've added custom features to your NanoClaw fork, and a new version is released upstream. Use this skill to pull in the new features and bug fixes while preserving your customizations.

Quick Start

Run the update-nanoclaw skill to synchronize upstream changes into your current installation.

Frequently Asked Questions about update-nanoclaw

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

FAQPage Schema
How do I sync upstream changes to a customized Git fork without losing local modifications?▼

To sync upstream changes without losing local modifications, the skill integrates updates via Git fetching, merging, or cherry-picking while guiding conflict resolution. It preserves your customizations by previewing changes and creating automated backups before applying upstream updates.

What is the safest way to merge upstream repository updates into a modified installation?▼

The safest way to merge upstream updates involves pre-update checks, automated backups, and conflict preview before applying changes. This process prevents data loss by requiring a clean working tree and validating the build after the upstream synchronization is complete.

Do I need a clean working tree to run a Git merge and sync upstream changes?▼

Yes, you need a clean working tree and Git access to the upstream repository to run the upstream sync. The skill performs pre-update checks and creates automated backups, requiring a clean state to safely manage merging, cherry-picking, and conflict resolution.

How do I preview upstream Git changes before merging them into my local fork?▼

You can preview upstream Git changes before merging by running the skill to fetch updates and evaluate the diff. It shows exactly what upstream changes will be applied and detects breaking changes before they are merged into your customized installation.

What happens if there are merge conflicts when syncing upstream repository updates?▼

If merge conflicts occur when syncing upstream updates, the skill guides you through resolving them efficiently. It previews conflicts before applying changes, manages Git operations safely, and detects breaking changes with optional migration skill execution to ensure build validation.

Related Skills

Explore More Software Engineering Skills→
nrupalanrupala

update-nanoclaw

Synchronize upstream NanoClaw changes into a customized install with rollback safeguards.

Community
Advanced
iia-argiia-arg

update-claudeclaw

Pull upstream ClaudeClaw updates into customized installations with conflict management and validation.

Community
Intermediate
erguotou520erguotou520

update-nanoclaw

Synchronize a NanoClaw fork with upstream changes while preserving local modifications.

Community
Advanced
thebrokencubethebrokencube
3

stacked-pr

Manage stacked branch workflows in Git with reset and cherry-pick propagation.

Community
Advanced