update-skills

Fetch upstream skill branches, merge selected updates, and validate with build/test.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of updating installed skill branches from upstream, ensuring you stay aligned with the latest changes without manual git churn.

Core Features & Use Cases

  • Preflight checks to ensure a clean working tree and valid upstream.
  • Detection of updated upstream branches under upstream/skill/* and evaluation of which skills have new commits.
  • Safe, selective updates with user-chosen merges and conflict resolution, followed by build and test validation.
  • Useful for teams maintaining a curated set of skills with custom tweaks, needing reproducible updates.

Quick Start

In Claude Code, run the update-skills flow to fetch upstream changes, select updated skills, and merge them into your local branches.

Frequently Asked Questions about update-skills

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

FAQPage Schema
How do I merge upstream changes into local git skill branches without manual conflicts?

This skill automates merging upstream changes into local git skill branches by fetching upstream/skill/* commits, evaluating which skills have new commits, and using --no-edit merges with conflict resolution and build validation.

What is the best way to keep installed git skills up to date from upstream?

Keeping installed git skills up to date from upstream is handled by this skill, which performs preflight checks, evaluates upstream/skill/* branches for new commits, and executes selective merges followed by build and test validation.

Does this skill update workflow require a clean working tree before merging?

Yes, this skill update workflow enforces preflight checks for a clean working tree and valid upstream before merging. This prevents accidental overwrites and ensures reproducible updates for teams maintaining curated skills.

Can I selectively choose which updated skill branches to merge from upstream?

Yes, you can selectively choose which updated skill branches to merge. The skill detects upstream/skill/* branches with new commits, allows user-chosen merges, resolves conflicts, and validates updates with build and test checks.

How do I resolve git merge conflicts when updating skill branches?

Resolving git merge conflicts when updating skill branches is handled by this skill, which merges upstream/skill/<name> using --no-edit, resolves conflicts during the automated flow, and validates stability with build and test checks.

What limitations exist when automating git skill updates from upstream?

Limitations of automating git skill updates from upstream include the requirement that skills are tracked as git branches under skill/* with a valid upstream, and preflight checks must pass to ensure a clean working tree before merging.