Analyze Claude Code releases and recommend plugin improvements
View on GitHubpsd401/psd-claude-coding-system
psd-claude-coding-system
plugins/psd-claude-coding-system/skills/claude-code-updates/SKILL.md
February 1, 2026
Select agents to install to:
npx add-skill https://github.com/psd401/psd-claude-coding-system/blob/main/plugins/psd-claude-coding-system/skills/claude-code-updates/SKILL.md -a claude-code --skill claude-code-updatesInstallation paths:
.claude/skills/claude-code-updates/# Claude Code Updates Analyzer Analyze recent Claude Code releases and identify improvements for this plugin. **Version Range:** $ARGUMENTS (or latest if empty) ## Workflow ### Phase 1: Gather Current Plugin State ```bash # Get current plugin version PLUGIN_DIR="$(dirname "$(dirname "$0")")" echo "=== Current Plugin State ===" cat "$PLUGIN_DIR/.claude-plugin/plugin.json" 2>/dev/null || echo "Plugin JSON not found" # Count current structure echo -e "\n=== Structure Counts ===" echo "Commands: $(find "$PLUGIN_DIR/commands" -name "*.md" 2>/dev/null | wc -l | tr -d ' ')" echo "Skills: $(find "$PLUGIN_DIR/skills" -type d -mindepth 1 2>/dev/null | wc -l | tr -d ' ')" echo "Agents: $(find "$PLUGIN_DIR/agents" -name "*.md" 2>/dev/null | wc -l | tr -d ' ')" # Sample frontmatter patterns echo -e "\n=== Frontmatter Patterns ===" head -10 "$PLUGIN_DIR/commands/work.md" 2>/dev/null | grep -E "^[a-z-]+:" || true ``` ### Phase 2: Fetch Claude Code Changelog Use WebFetch to retrieve the Claude Code changelog: **Primary Source:** https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md **Fallback Sources:** - https://docs.anthropic.com/claude-code/changelog - https://www.anthropic.com/news (filter for Claude Code) **Focus Areas for Analysis:** 1. **Skills/Commands Architecture** - New frontmatter fields - Skills directory structure changes - Command deprecations - `context: fork` and `agent` field support 2. **Hooks System** - New hook events - Per-skill hooks in frontmatter - Hook parameter changes 3. **Tool Permissions** - `allowed-tools` syntax changes - New tools available - Permission model updates 4. **Model Updates** - New model IDs available - Model deprecations - Extended thinking changes 5. **Breaking Changes** - API changes - Configuration format changes - Plugin structure requirements ### Phase 3: Analyze Plugin Compatibility For each relevant change found: 1. **Check if plugin implements the feat