update-skills

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skills distributed as git branches require manual checks for upstream updates, merging, conflict resolution, and post-update validation, which is time-consuming and error-prone when managing multiple installed skills.

Core Features & Use Cases

  • Preflight Checks: Automatically verifies a clean working tree and configured upstream remote before proceeding.
  • Update Detection: Identifies which installed skills have new upstream commits, which are up to date, and which are not installed.
  • Interactive Selection: Lets you choose which skills to update via a multi-select prompt.
  • Automated Merge & Validation: Merges selected skill branches, resolves conflicts where possible, and runs build/test checks to ensure functionality.
  • Use Case: If you have 5 installed NanoClaw skills, this skill automatically checks for updates, lets you pick which to apply, handles merge issues, and confirms the update didn't break your setup.

Quick Start

Use the update-skills skill to check for and apply available updates to your installed NanoClaw skill branches from upstream.

Frequently Asked Questions about update-skills

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

FAQPage Schema
How do I automate git merge updates for multiple installed skill branches?

Automating git merge updates for skill branches requires a clean local working tree and a configured upstream remote. The process detects new upstream commits, interactively prompts for skill selection, and executes an automated merge with conflict resolution and post-update build validation.

What's the best way to check if my installed git branches have new upstream commits?

Checking for new upstream commits on installed git branches involves verifying a clean working tree and configured upstream remote. The detection process then categorizes installed skills by update availability, identifying branches with new commits versus those already up to date.

Do I need a clean working tree to merge upstream skill updates?

A clean local git working tree is required to merge upstream skill updates. Preflight repository checks enforce this prerequisite alongside a configured upstream remote, preventing the automated merge and conflict resolution workflow from overwriting uncommitted local changes.

Can I choose which specific skill branches to update instead of applying all upstream changes?

Choosing specific skill branches to update is supported via an interactive multi-select prompt. The system presents installed skills alongside their upstream update status, enabling selective application of changes rather than forcing a bulk update of all branches simultaneously.

How does build validation work after merging upstream skill branches?

Build validation after merging upstream skill branches executes post-update build and test checks using standard git and pnpm tooling. This automated step confirms the merged updates maintain functional integrity and did not break the existing local setup.

What happens if there are merge conflicts when updating skill branches?

Merge conflicts during skill branch updates are handled by automated resolution where possible. If the system cannot resolve a conflict automatically, the workflow pauses to allow manual file manipulation and conflict resolution before continuing to post-update build validation.