Help us improve
Share bugs, ideas, or general feedback.
From project-plugin
Analyzes Claude Code changelog for breaking changes, new features, deprecations, and impacts on plugins. Identifies required updates and opportunities after releases.
npx claudepluginhub laurigates/claude-plugins --plugin project-pluginHow this skill is triggered — by the user, by Claude, or both
Slash command
/project-plugin:changelog-reviewhaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Expertise for analyzing Claude Code changelog and identifying impacts on plugin development.
Scan Claude Code changelog for new versions, features, and changes. Fetches official docs, parses release notes, and generates structured update report.
Reviews Claude Code release notes, filtering for relevance to your installed plugins, skills, tools, and platform. Use for 'what's new?', update checks, or changelog queries.
Fetches Claude Code GitHub release notes via gh CLI, filters out bug fixes, summarizes Added/Improved/Changed/Deprecated items in Chinese, detects running session version with lsof on PPID. Useful for update overviews.
Share bugs, ideas, or general feedback.
Expertise for analyzing Claude Code changelog and identifying impacts on plugin development.
Review Claude Code releases to:
| Category | Example Changes | Action |
|---|---|---|
| Breaking changes | API changes, renamed tools | Update affected plugins immediately |
| Security fixes | Permission vulnerabilities | Review and update permission rules |
| Deprecations | Removed features/fields | Remove deprecated usage |
| Hook changes | New events, schema changes | Update hooks-plugin |
| Category | Example Changes | Action |
|---|---|---|
| New features | New tools, frontmatter fields | Consider plugin enhancements |
| Permission updates | New wildcard patterns | Update permission documentation |
| SDK changes | New callbacks, streaming | Update SDK-related skills |
| MCP improvements | OAuth, server configs | Update agent-patterns-plugin |
| Category | Example Changes | Action |
|---|---|---|
| Bug fixes | UI improvements | Note in changelog |
| Performance | Startup optimizations | No action needed |
| IDE features | VS Code updates | No action needed |
Map changelog categories to plugins:
| Claude Code Area | Affected Plugins |
|---|---|
| Hooks | hooks-plugin, configure-plugin |
| Skills/Commands | All plugins with skills/commands |
| Agents | agents-plugin, agent-patterns-plugin |
| MCP servers | agent-patterns-plugin |
| Permissions | configure-plugin, hooks-plugin |
| Git operations | git-plugin |
| Testing tools | testing-plugin |
| SDK changes | agent-patterns-plugin |
Version state stored in .claude-code-version-check.json:
{
"lastCheckedVersion": "2.1.7",
"lastCheckedDate": "2026-01-14",
"changelogUrl": "https://raw.githubusercontent.com/anthropics/claude-code/main/CHANGELOG.md",
"reviewedChanges": [
{
"version": "2.1.7",
"date": "2026-01-14",
"relevantChanges": [],
"actionsRequired": []
}
]
}
# Read last checked version
cat .claude-code-version-check.json | jq -r '.lastCheckedVersion'
Use WebFetch to get the current changelog from:
https://raw.githubusercontent.com/anthropics/claude-code/main/CHANGELOG.md
Compare fetched changelog versions against lastCheckedVersion. Extract all changes since that version.
For each change, determine:
Produce a report with:
Update .claude-code-version-check.json with:
Look for:
Look for:
Look for:
Look for:
Look for:
# Claude Code Changelog Review
**Review Date**: YYYY-MM-DD
**Versions Reviewed**: X.X.X to Y.Y.Y
**Previous Check**: YYYY-MM-DD (vX.X.X)
## Summary
- **New versions**: N
- **High-impact changes**: N
- **Medium-impact changes**: N
- **Action items**: N
## High-Impact Changes
### [Version] - Change Title
**Impact**: Breaking/Security/Deprecation
**Affected plugins**: plugin1, plugin2
**Required action**: Description of what needs to be done
## Medium-Impact Changes
### [Version] - Change Title
**Impact**: New feature/Enhancement
**Opportunity**: How plugins could benefit
**Suggested plugins**: plugin1, plugin2
## Action Items
- [ ] Item 1 (high priority)
- [ ] Item 2 (medium priority)
## Next Steps
1. Create issues for high-priority items
2. Schedule review of medium-impact changes
3. Update version tracking file
For GitHub Actions workflow:
Claude Code uses semantic versioning: MAJOR.MINOR.PATCH
| Label | Use For |
|---|---|
changelog-review | All changelog-related issues |
breaking-change | Breaking changes requiring updates |
enhancement | New feature opportunities |
maintenance | General housekeeping |