Changelog

Variables

Arguments: $ARGUMENTS

Scope

Ingests Claude Code changelog entries and integrates them into the repo. Covers the full arc: read upstream changes → orient on repo impact → research new features → triage with user → plan edits → implement → verify → close matching issues.

Distinct from:

• /known-issues — tracks CC bugs/workarounds. This skill integrates CC feature changes into repo config/docs
• Any release-triage automation the consumer runs (issue filing per release) — this skill IMPLEMENTS changes, holistically across a release

Input modes

Three ways to provide changelog content (priority order):

1. User pastes text — skill parses inline changelog from conversation context
2. Specific version — /changelog apply v2.1.152 fetches that version from code.claude.com/docs/en/changelog
3. Auto-detect latest — /changelog apply (no version) automatically fetches changelog, identifies latest version, and proceeds

Version awareness

On every apply or diff invocation, compare the target version against the active terminal's CC version, captured at load:

• Installed CC version: !claude --version || echo "(CC version unavailable)"

• If target version > installed version: warn user — "You're applying v2.1.152 changes but running v2.1.150. Update CC first (claude update) or changes may reference features not yet available in your session."
• If target version = installed version: proceed normally
• If target version | P1 | | |

| 2 | | P2 | — | | | N | | P3 | — | No action |

User picks scope: "all P1+P2", "just P1", or specific items by number.

Lock brief: confirmed scope becomes implementation contract.

### Phase 4 — Plan

Plan concrete edits with cross-cutting awareness:

1. Group changes by file (multiple items may touch same file)
2. Identify cross-cutting dependencies (e.g., a new hook event may need updates in every surface that documents hook events — rules, hook scripts, and reference docs alike)
3. Order edits to avoid conflicts
4. For each file: specific section to edit, old text to replace, new text

### Phase 5 — Implement

Execute plan:

1. Edit files per the approved plan
2. Run the consumer repo's markdown linter on every touched `.md` file (e.g. `npx markdownlint-cli2`), when one is configured
3. If hook scripts touched: run their tests with the consumer repo's test runner
4. If settings.json touched: `jq empty .claude/settings.json`

### Phase 6 — Verify

Run the consumer repo's verification workflow (build/test/lint) on affected ecosystems. At minimum: markdown lint on all touched files.

### Phase 7 — Close issues (optional)

If user approves:

1. If the consumer repo files CC-release tracking issues, search for matching open ones using
   that repo's own convention (label, title marker, or milestone) via `gh issue list --state open --search '...'`
2. For each issue whose title matches an implemented changelog item: close with comment citing this session's work

---

## Actions: fetch, diff, status (read-only)

The three read-only actions stop short of any edit — **full steps in [context/read-actions.md](context/read-actions.md)**:

- **`fetch`** — WebFetch + display a version (or latest, or a `v.X..v.Y` range) of `code.claude.com/docs/en/changelog`. No edits
- **`diff`** — dry run of `apply`: Phase 0 (ingest) + Phase 1 (explore) + Phase 2 (research), stops before interview. Emits the triage table only. Answers "is this release worth an `apply`?"
- **`status`** — applied versions (`git log --grep`), open routine-pipeline issues (`gh issue list`), current `claude --version`, and the gap if installed > last-applied

---

## Cross-references

- `context/repo-surfaces.md` — surface categories to check per changelog item
- `context/classification-rubric.md` — P1/P2/P3 classification criteria
- `context/read-actions.md` — full steps for the read-only actions

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [melodic-software](https://github.com/melodic-software)
- **Source:** [melodic-software/claude-code-plugins](https://github.com/melodic-software/claude-code-plugins)
- **License:** MIT

Install and usage instructions live in the source repository linked above.