changelog-scan
npx machina-cli add skill fusengine/agents/changelog-scan --openclawChangelog Scan Skill
Overview
Fetches and analyzes the official Claude Code changelog to detect new versions and changes.
Data Sources
| Source | URL | Method |
|---|---|---|
| Changelog | code.claude.com/docs/en/changelog.md | WebFetch |
| Docs Index | code.claude.com/docs/llms.txt | WebFetch |
| Hooks Ref | code.claude.com/docs/en/hooks.md | WebFetch |
| Plugins Ref | code.claude.com/docs/en/plugins-reference.md | WebFetch |
| CLI Ref | code.claude.com/docs/en/cli-reference.md | WebFetch |
Workflow
- Fetch changelog via WebFetch or scripts/fetch-changelog.sh
- Parse version numbers and release dates
- Extract changes per version (features, fixes, breaking)
- Compare with last known version from state file
- Generate report using templates/changelog-report.md
Version Detection
Parse patterns from changelog:
## vX.Y.Zor## X.Y.Z- Version headers### Breaking Changes- Breaking section### New Features- Features section### Bug Fixes- Fixes section
State File
Location: ~/.claude/logs/00-changelog/{date}-state.json
References
Source
git clone https://github.com/fusengine/agents/blob/main/plugins/changelog-watcher/skills/changelog-scan/SKILL.mdView on GitHub Overview
The skill fetches Claude Code’s official changelog and docs, parses version headers and release sections, and detects new versions, features, and breaking changes. It then generates a structured update report to streamline upgrade planning and communication.
How This Skill Works
Data sources include the Changelog, Docs Index, Hooks, Plugins, and CLI references accessed via WebFetch. The tool parses version headers like '## vX.Y.Z' or '## X.Y.Z' and sections such as '### New Features', '### Bug Fixes', and '### Breaking Changes'. It compares the current version against a stored state and renders a report with templates/changelog-report.md.
When to Use It
- To track Claude Code releases and understand new versions before upgrading
- When you need features, fixes, or breaking changes highlighted for customers
- In CI/CD or release pipelines to automate changelog-driven checks
- For historical release analysis by comparing with the last known version
- When preparing upgrade notes or documentation for stakeholders
Quick Start
- Step 1: Fetch changelog via WebFetch or scripts/fetch-changelog.sh
- Step 2: Parse version headers and sections (New Features, Bug Fixes, Breaking Changes)
- Step 3: Generate the report using templates/changelog-report.md and save the updated state
Best Practices
- Use the version headers '## vX.Y.Z' or '## X.Y.Z' as the primary signal
- Verify breaking, feature, and bug-fix sections align with the standard headings
- Keep a local state file at ~/.claude/logs/00-changelog/{date}-state.json
- Validate the generated report against templates/changelog-report.md
- Schedule regular runs and respect any rate limits for the sources
Example Use Cases
- Detect v2.3.0 and extract its features and fixes
- Flag breaking changes before upgrading a deployment
- Produce a structured update report for a release
- Compare current vs previous version using the state file
- Incorporate docs index context to enrich notes
