skills.rest
wrightchin
wrightchinCOMMUNITY
Explore all skills by this author →
GitHub

update-nanoclaw

Synchronize NanoClaw forks with upstream updates while preserving local customizations.

Updated Apr 26, 2026
Search Tags:#rollback#merge#rebase#cherry-pick#conflicts#upstream#nanoclaw
One-click install
npx skills add https://github.com/wrightchin/nanoclaw-playground --skill update-nanoclaw-wrightchin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-nanoclaw
Source: https://github.com/wrightchin/nanoclaw-playground/tree/main/.claude/skills/update-nanoclaw
Command: npx skills add https://github.com/wrightchin/nanoclaw-playground --skill update-nanoclaw-wrightchin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Your NanoClaw fork drifts from upstream as you customize it. This skill pulls upstream changes into your install without losing your modifications.

Core Features & Use Cases

  • Preflight checks ensure a clean working tree and remote setup, and automatically determine the upstream branch.
  • Backup and rollback points are created before touching anything.
  • Preview changes from upstream, with clear categorization of affected areas and suggested strategies (merge, cherry-pick, rebase).
  • Conflict handling, validation, and breaking-change checks to minimize risk.
  • Optional migration steps for breaking changes and integration with existing skill workflows.

Quick Start

Run /update-nanoclaw in Claude Code.

Frequently Asked Questions about update-nanoclaw

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

FAQPage Schema
How do I merge upstream changes into a fork without losing local customizations?▼

Merging upstream changes without losing local customizations requires preflight dirty-tree checks, backup rollback points, conflict previews, and applying updates via merge, cherry-pick, or rebase strategies to preserve your local modifications.

What is the best way to handle upstream conflicts during a fork rebase?▼

Handling upstream conflicts during a fork rebase involves generating token-aware diffs, previewing affected areas, and validating breaking changes against the CHANGELOG before finalizing the upgrade in your containerized environment.

Can I preview breaking changes before pulling upstream updates into my fork?▼

Yes, you can preview breaking changes before pulling upstream updates because this skill categorizes affected areas, checks the CHANGELOG for breaking changes, and suggests appropriate update strategies before touching your working tree.

How do I rollback a failed cherry-pick upgrade in a containerized environment?▼

To rollback a failed cherry-pick upgrade, this skill automatically creates backup rollback points before applying any upstream changes, allowing you to restore your previous working tree state if the update fails.

When should I use cherry-pick instead of merge for upstream synchronization?▼

You should use cherry-pick instead of merge for upstream synchronization when you need to selectively apply specific upstream commits while leaving other changes behind, whereas merge integrates the entire upstream branch history.

Why does my upstream synchronization fail on a dirty working tree?▼

Upstream synchronization fails on a dirty working tree because the skill enforces strict preflight checks requiring a clean working state and proper remote setup before attempting any merge, rebase, or cherry-pick operations.

Related Skills

Explore More Software Engineering Skills→
chiptoe-svgchiptoe-svg

update-skills

Detect and merge upstream updates for git branch-distributed skills.

Community
Intermediate
breakcafebreakcafe
1

update-nanoclaw

Merge upstream NanoClaw updates into customized Git forks with preflight checks and rollback.

Official
Advanced
jboothomasjboothomas
1

update-nanoclaw

Merge upstream NauggieClaw updates into customized forks with backups and conflict previews.

Community
Advanced
spyqsspyqs

update-nanoclaw

Synchronize a customized NanoClaw fork with upstream updates via merge, cherry-pick, or rebase.

Community
Advanced