update-skills

Detect and update installed skill branches from upstream Git.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/OfirGavish/NinjaClaw-Nano --skill update-skills-ofirgavish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-skills
Source: https://github.com/OfirGavish/NinjaClaw-Nano/tree/main/.copilot/skills/update-skills
Command: npx skills add https://github.com/OfirGavish/NinjaClaw-Nano --skill update-skills-ofirgavish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates checking upstream for newer commits on installed skill branches and guides safe updates to keep your environment synchronized with upstream changes, while preserving local customizations.

Core Features & Use Cases

  • Preflight checks ensure a clean working tree and correct remotes before attempting updates.
  • Detection & Selection lists upstream skill/* branches, determines which are merged, and identifies those with new commits for targeted updates.
  • Update & Validation applies selected updates via git merge, resolves conflicts when possible, and runs build/test validation to ensure integrity.
  • Use Case: a developer maintains several installed skills; this tool helps keep them current without breaking local changes.

Quick Start

Run the /update-skills command in Copilot to fetch upstream updates and apply them to your installed skills.

Frequently Asked Questions about update-skills

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

FAQPage Schema
How do I automatically update installed skills from upstream Git branches?

Updating installed skills from upstream involves preflight checks for clean remotes, detecting new commits on upstream skill branches, and executing git merges with conflict handling and build validation to preserve local customizations.

Can I sync upstream skill branches without losing local modifications?

Yes, syncing upstream skill branches preserves local modifications by enforcing dry-run checks, automated conflict handling, and build validation to ensure local customizations are maintained during the git merge process.

What is the safest way to apply git merges for upstream skill updates?

The safest way to apply git merges for upstream skill updates is to use preflight checks, dry-run validation, and conflict handling to ensure a clean working tree and preserve local customizations.

How do preflight checks work when detecting new commits on upstream branches?

Preflight checks work by verifying a clean working tree and correct remotes before detecting new commits on upstream skill branches, ensuring the environment is safe for applying updates.

Does the update-skills workflow support dry-run checks before merging?

Yes, the update-skills workflow supports dry-run checks before merging, enforcing a safe workflow that includes conflict handling and build validation to preserve local customizations.

Why does upstream skill update validation fail after a git merge?

Upstream skill update validation may fail after a git merge if build or test validation detects integrity issues, preventing updates with unresolved conflicts or broken builds from being applied to local customizations.