Help us improve
Share bugs, ideas, or general feedback.
From plugin-upgrade
Use this skill when the user asks about "plugin management", "plugin upgrade issues", "plugin troubleshooting", "plugin version", "plugin not working after upgrade", "rollback plugin", "downgrade plugin", or has problems with Claude Code plugins. Provides guidance on managing, upgrading, and troubleshooting Claude Code plugins.
npx claudepluginhub sontixyou/claude-code-plugin-upgrader --plugin plugin-upgradeHow this skill is triggered — by the user, by Claude, or both
Slash command
/plugin-upgrade:plugin-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides guidance for managing Claude Code plugins, including installation, upgrading, troubleshooting, and best practices.
Troubleshoots Claude Code plugin registry issues like installation scopes, orphaned entries, project-scoped visibility bugs, and debugging failures. Details structure of ~/.claude/plugins/installed_plugins.json.
Upgrades Claude Code plugins by aligning skills, hooks, and patterns with latest capabilities and best practices. Use after updates, for modernization, or on user request.
Guides Claude Code plugin setup including directory structure, plugin.json manifest, component organization for commands/agents/skills/hooks, auto-discovery, and naming conventions.
Share bugs, ideas, or general feedback.
This skill provides guidance for managing Claude Code plugins, including installation, upgrading, troubleshooting, and best practices.
Claude Code plugins are stored in these locations:
| Location | Description |
|---|---|
~/.claude/plugins/ | User-installed plugins |
~/.claude/plugins/cache/ | Marketplace plugins (managed by Claude Code) |
.claude-plugin/ | Project-local plugins |
Plugins installed from Git repositories:
git pullUpgrade method:
cd ~/.claude/plugins/<plugin-name>
git fetch --all
git pull origin main
Official plugins from Claude Code marketplace:
~/.claude/plugins/cache/claude-plugins-official/claude plugins update <plugin-name>Plugins created or copied locally:
Check plugin structure:
.claude-plugin/plugin.json existsname field is presentVerify installation:
ls -la ~/.claude/plugins/<plugin-name>/
cat ~/.claude/plugins/<plugin-name>/.claude-plugin/plugin.json
Check Claude Code logs:
claude --debug
Check for breaking changes:
Rollback to previous version:
cd ~/.claude/plugins/<plugin-name>
git log --oneline # Find previous commit
git checkout <commit-hash>
Or checkout specific tag:
git tag -l # List available tags
git checkout v1.0.0 # Checkout stable version
Check command file location:
commands/ directory.md extensionVerify YAML frontmatter:
---
description: Command description
---
Restart Claude Code:
Verify hooks.json syntax:
cat ~/.claude/plugins/<plugin-name>/hooks/hooks.json | jq .
Check hook scripts are executable:
chmod +x ~/.claude/plugins/<plugin-name>/hooks/scripts/*.sh
Test hooks with debug mode:
claude --debug
Upgrade one plugin at a time, test after each:
/plugin-upgrade:checkUpgrade multiple plugins at once:
/plugin-upgrade:check/plugin-upgrade:upgrade to select multipleBefore upgrading, prepare rollback:
| Issue | Solution |
|---|---|
| "Plugin not found" | Check plugin directory exists and has valid plugin.json |
| "Command not recognized" | Restart Claude Code, verify command file exists |
| "Hook timeout" | Increase timeout in hooks.json or optimize hook script |
| "Git pull failed" | Check for local changes, try git stash first |
| "Permission denied" | Run chmod +x on script files |
If you encounter persistent issues:
claude --debug for detailed logs