How do I install the Changelog Scan skill?

Run npx skillmds@latest add fusengine/changelog-scan-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Changelog Scan skill do?

Use when checking for new Codex versions, features, or changes since the last known release. It is listed under Coding & Dev Tools, Docs & Writing on SkillMD.

Is Changelog Scan safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Changelog Scan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Changelog Scan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Changelog Scan?

fusengine (@fusengine) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Changelog Scan by fusengine — Agent Skill

Name: Changelog Scan
Author: fusengine

File contents

Changelog Scan Skill

Overview

Fetches and analyzes the official Codex 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 the harness CLI (ported from the old fetch-changelog into @fusengine/harness): bun ${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 ~/.codex/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.
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.Z or ## X.Y.Z - Version headers
### Breaking Changes - Breaking section
### New Features - Features section
### Bug Fixes - Fixes section

State File

Location: ~/.codex/logs/00-changelog/{date}-state.json

References

Sources Reference
Report Template

---name: changelog-scan-2description: Use when checking for new Codex versions, features, or changes since the last known release.---<objective>Fetches the official Codex 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 (`~/.codex/logs/00-changelog/<date>-state.json`), and generates a structured update report using `references/templates/changelog-report.md`.</objective># Changelog Scan Skill## OverviewFetches and analyzes the official Codex 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 |## Workflow1. **Fetch** changelog via the harness CLI (ported from the old `fetch-changelog` into `@fusengine/harness`): `bun ${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 `~/.codex/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 dates3. **Extract** changes per version (features, fixes, breaking)4. **Compare** with last known version from state file5. **Generate** report using templates/changelog-report.md## Version DetectionParse 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 FileLocation: `~/.codex/logs/00-changelog/{date}-state.json`## References- [Sources Reference](references/sources.md)- [Report Template](references/templates/changelog-report.md)

Frequently asked questions

Changelog Scan