upgrade-plugin

Upgrading Claude Code plugins involves analyzing the plugin's directory to detect deprecated hooks, skills, and agents, then generating a curated upgrade plan. This automated process aligns your plugin with the latest platform features and best practices.

Auditing a plugin for deprecated Claude Code patterns requires an automated obsolescence screening of its skills, hooks, and agents. This process flags superseded elements and generates a comprehensive upgrade plan with prioritized actions.

Yes, internet connectivity is required to modernize your Claude Code plugin. The automated upgrade process fetches recent changelogs, documentation, and model updates to accurately detect deprecated patterns and apply best-practice modifications.

Yes, you can automatically apply an upgrade plan to modify your plugin files. After generating a curated plan with prioritized actions, an execution workflow applies the approved changes, updates the version bump, and verifies compliance.

Your Claude Code plugin upgrade requires directory access to comprehensively audit the plugin’s structure, skills, hooks, output styles, and test coverage. This permission enables the execution workflow to apply approved changes and modify files directly.

You should avoid automating a Claude Code plugin upgrade if your plugin lacks test coverage or if you cannot verify compliance after the execution workflow applies modifications. Manual updates are safer for highly customized or undocumented plugin structures.