# Changelog Scan

> Use when checking for new Claude Code versions, features, or changes since the last known release.

- Skill: `fusengine/changelog-scan` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add fusengine/changelog-scan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/fusengine/changelog-scan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools, Docs & Writing
- Author: fusengine (https://skillmd.com/u/fusengine)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/fusengine/changelog-scan

---


<objective>
Fetches the official Claude Code changelog via the harness CLI's `changelog` command (ported from the old `fetch-changelog`, WebFetch on `code.claude.com/docs/en/changelog.md` as manual fallback), parses version headers and per-version changes (features/fixes/breaking), compares against the last known version recorded in the state file (`~/.claude/logs/00-changelog/<date>-state.json`), and generates a structured update report using `references/templates/changelog-report.md`.
</objective>

# Changelog 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

1. **Fetch** changelog via the harness CLI (ported from the old `fetch-changelog` into `@fusengine/harness`):
   `bun ${CLAUDE_PLUGIN_ROOT}/../node_modules/@fusengine/harness/dist/cli/bin.mjs changelog`
   It fetches `code.claude.com/docs/en/changelog.md`, parses versions (current MDX `<Update label="X.Y.Z">` format + legacy `## vX.Y.Z` fallback), writes state to `~/.claude/logs/00-changelog/<date>-state.json`, and prints JSON `{latest, new_since_last_check, recent_versions}`. WebFetch on the same URL is the manual fallback.
2. **Parse** version numbers and release dates
3. **Extract** changes per version (features, fixes, breaking)
4. **Compare** with last known version from state file
5. **Generate** report using templates/changelog-report.md

## Version Detection

Parse patterns from changelog:
- `## vX.Y.Z` or `## 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

- [Sources Reference](references/sources.md)
- [Report Template](references/templates/changelog-report.md)

