update-plugin

Updates the installed Claude Code plugin to the latest branch state and reports changed skills.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/sagittaras/agentic-workflow --skill update-plugin-sagittaras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-plugin
Source: https://github.com/sagittaras/agentic-workflow/tree/main/skills/update-plugin
Command: npx skills add https://github.com/sagittaras/agentic-workflow --skill update-plugin-sagittaras

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Keeping a git-installed Claude Code plugin current is error-prone: users do not know whether new commits arrived, which skills changed, or whether a reload or full restart is required. This Skill pulls the latest state of the branch the installation tracks and translates the result into a clear report with concrete next steps. ## Core Features & Use Cases - Safe update via script: Delegates the pull to the plugin's own installer, which verifies the remote and enforces fast-forward-only merges, so no history is rewritten. - Change reporting: Lists added, modified, and removed skills plus all changed files, and advises whether /reload-plugins suffices or a restart is needed. - Edge-case handling: Detects dirty installations, detached HEAD, branches without a remote counterpart, and unpushed or unmerged work sitting in a separate development clone. - Use Case: After a teammate pushes new skills to the plugin repository, run this Skill to fetch them, see exactly which skills appeared, and learn whether you must restart Claude Code. ## Quick Start Ask the assistant to update the sagittaras plugin and tell you which skills changed and whether a reload or restart is needed.

Frequently Asked Questions about update-plugin

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

FAQPage Schema
How do I update a Claude Code plugin installed from git?

Invoke the update-plugin skill, which runs the plugin's update script to pull the latest commits on the tracked branch. It reports which skills changed and tells you whether to run /reload-plugins or restart Claude Code.

How do I know if a plugin update needs a restart or just a reload?

If only existing skills were modified, /reload-plugins is sufficient. When skills were added or removed, a full restart of Claude Code is the reliable option, since reload is built for changes to files already on disk.

Why does the plugin update skip downloading changes?

The update is skipped when the installation has uncommitted local changes, reported as install_dirty=true. Save or discard those changes first, then run the update again; the skill never overwrites local work.

What happens if the installed branch does not exist on the remote?

The script reports reason=branch_not_on_remote and exits cleanly without pulling. This is not an error; the installation simply sits on a purely local branch, so there is nothing to download until you switch to a tracked branch.

Can the update skill lose unpushed work from my development clone?

No data is lost, but the skill warns when a separate development clone of the same repository has dirty, unpushed, or unmerged work. The installation only pulls its own tracked branch, so such work stays invisible to it.