/changelog-scan
Use when checking for new Claude Code versions, features, or changes since the last known release.
$ npx -y skills add fusengine/agents --skill changelog-scan --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/changelog-scan
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when checking for new Claude Code versions, features, or changes since the last known release.
SKILL.md
changelog-scan.SKILL.mdname: changelog-scan
description: "Use when checking for new Claude Code versions, features, or changes since the last known release."
argument-hint: "[--since <version>]"
user-invocable: true
<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)
Read more
name: changelog-scan description: "Use when checking for new Claude Code versions, features, or changes since the last known release." argument-hint: "[--since <version>]" user-invocable: true
<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)
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill

