[FEATURE] Plugin/skill auto-update check before execution

Resolved 💬 2 comments Opened Mar 23, 2026 by RamboWasReal Closed Apr 21, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When invoking a skill from a marketplace plugin (e.g. /preflight-setup), Claude Code should check if the marketplace repo has a newer version of the plugin and
prompt the user to update if so. Currently, skills are cached locally after /plugin install and never update unless manually reinstalled. This means users can run
outdated skills without knowing a fix or improvement exists.

Suggested behavior:

  • On skill invocation, compare local plugin commit hash with remote HEAD
  • If outdated: show "Plugin update available. Run /plugin install X@marketplace to update." before executing
  • Optional: add /plugin update command to update all or specific plugins

Proposed Solution

When a user invokes a skill from a marketplace plugin (e.g. /preflight-setup), Claude Code should automatically check if the marketplace repository has a newer
version before executing.

Ideal flow:

  1. User types /preflight-setup
  2. Claude Code does a quick git ls-remote on the marketplace repo and compares with the locally cached commit
  3. If outdated, show a prompt: ⚠ Plugin "react-native-preflight" has updates available. Update now? (y/n)
  4. If user accepts, run /plugin install react-native-preflight@marketplace-name automatically, then execute the skill
  5. If user declines, execute the cached version as-is

Additionally, a /plugin update command would be useful:

  • /plugin update — update all installed marketplace plugins
  • /plugin update react-native-preflight — update a specific plugin

Currently, plugins are cached locally after /plugin install and never update unless manually reinstalled. Users run outdated skills without knowing fixes or
improvements exist upstream.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗