update-nanoclaw

Merge upstream NanoClaw changes into customized installs with rollback points.

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

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 to ensure a clean working tree and proper remotes; backup and timestamped rollback points; multiple merge strategies (merge, cherry-pick, rebase); conflict preview and guided resolution; automated validation with build and tests; breaking-change detection with migration prompts.
  • Use in scenarios where you want to safely incorporate upstream NanoClaw updates while preserving local changes, or selectively cherry-pick commits that matter, with low token usage and rollback safety.
  • Use Case: As a maintainer with a customized NanoClaw install, you can fetch upstream updates, preview conflicts, perform a controlled merge or selective cherry-picks, validate builds, and apply any necessary migrations or skill-based breakage migrations.

Quick Start

Run the /update-nanoclaw command in Claude Code to begin updating your NanoClaw fork with upstream changes, including backup, conflict preview, and optional migration steps.

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 customized NanoClaw fork without overwriting local modifications?

To merge upstream changes safely, the skill performs preflight checks, creates timestamped backups, previews conflicts, and offers merge, cherry-pick, or rebase strategies to integrate updates while preserving your local NanoClaw modifications.

What is the best way to rollback a failed upstream merge in NanoClaw?

The safest way to rollback a failed upstream merge is using the skill's timestamped backup points created during preflight, allowing you to revert your NanoClaw install to its previous state before the update attempt.

Can I selectively cherry-pick upstream commits into my NanoClaw install?

Yes, you can selectively cherry-pick upstream commits, as the skill provides cherry-pick as one of its merge strategy options alongside standard merge and rebase, enabling controlled integration of specific upstream changes.

Does the NanoClaw update process detect breaking changes and apply migrations?

Yes, the update process includes automated breaking-change detection with migration prompts, validating builds and tests before finalizing the upstream merge to ensure your customized NanoClaw install remains functional.

What should I check before pulling upstream NanoClaw changes into my local fork?

Before pulling upstream NanoClaw changes, ensure you have a clean working tree and properly configured git remotes, as the skill's preflight checks validate these conditions before creating backups and proceeding with the merge.