update-skills

Detect and update installed skill branches from upstream with conflict handling.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This capability detects and updates installed skill branches from upstream, reducing drift and keeping your skillset current without breaking local customizations.

Core Features & Use Cases

  • Preflight checks ensure a clean working tree and correct remotes before any update.
  • Detection and listing of upstream skill updates across all installed skills.
  • User-guided selection of which skills to update, with conflict-aware merging and reconciliation.
  • Post-merge validation via build and tests to verify integrity.

Quick Start

Run update-skills in Claude Code

Frequently Asked Questions about update-skills

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

FAQPage Schema
How do I update installed skill branches from upstream?

To update installed skill branches from upstream, you can run a process that performs preflight checks, fetches upstream changes, and merges selected branches using --no-edit to keep your skillset current.

What is the safest way to merge upstream skill updates without losing local customizations?

Safely merging upstream skill updates involves running preflight checks for a clean working tree, selecting specific skills to update, and using conflict-aware reconciliation to preserve your local customizations.

Can I choose which installed skills to update when fetching from upstream?

Yes, you can selectively choose which installed skills to update through a user-guided selection process that detects available upstream updates and lets you pick specific branches to merge.

How does conflict handling work when merging upstream skill branches?

Conflict handling during upstream merges uses conflict-aware reconciliation, allowing you to manage discrepancies between local customizations and fetched upstream changes before finalizing the merge.

Does updating skills from upstream validate the merge with tests?

Yes, updating skills from upstream validates the merge by running post-merge build and test checks to verify the integrity of the updated skill branches.

Why do I need a clean working tree before updating skill branches?

A clean working tree is required before updating skill branches because preflight checks ensure correct remotes and prevent local conflicts from corrupting the upstream merge process.