refresh-patches

Audit upstream NemoClaw changes and reapply patch fragments.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/stevenrick/nemoclaw-cookbook --skill refresh-patches
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refresh-patches
Source: https://github.com/stevenrick/nemoclaw-cookbook/tree/main/.claude/skills/refresh-patches
Command: npx skills add https://github.com/stevenrick/nemoclaw-cookbook --skill refresh-patches

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upstream NemoClaw can introduce changes that break our patches; this skill provides a disciplined workflow to audit, align, and reapply patches so downstream customizations stay compatible.

Core Features & Use Cases

  • Upstream overlap audits to identify breaking changes and deprecated patch content.
  • Diagnose failures in apply-patches.sh and restore a clean state for patch reapplication.
  • Update fragments and reference material to maintain compatibility with newer upstream releases.

Quick Start

Run the patch maintenance workflow to audit upstream changes and reapply fragments as needed, ensuring the patched environment remains consistent with upstream.

Frequently Asked Questions about refresh-patches

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

FAQPage Schema
How do I fix apply-patches.sh when upstream NemoClaw changes break my cookbook fragments?

To fix apply-patches.sh failures, audit the upstream NemoClaw changes to identify breaking overlaps, then reapply the updated YAML fragments to restore downstream compatibility.

What is the best way to maintain downstream patches when upgrading to a newer upstream release?

The best way to maintain patches during an upstream upgrade is to perform an upstream overlap audit, remove deprecated patch content, and update YAML fragments to align with the new upstream baseline.

When do I need to refresh upstream patches in my NemoClaw workflow?

You need to refresh upstream patches when upstream NemoClaw introduces breaking changes, deprecates content you previously patched, or when your existing apply-patches.sh workflow starts failing.

Do I need specific script sets to update NemoClaw cookbook fragments?

Yes, updating NemoClaw cookbook fragments requires the script set and policy fragments in patches/fragments, the apply-patches.sh workflow, and downstream validation scripts.

Why does upstream NemoClaw overlap break my patched environment?

Upstream NemoClaw overlap breaks patched environments because upstream releases introduce features that conflict with customizations, requiring YAML fragment updates to maintain compatibility.