changeloglisted

Ingest Claude Code changelog entries and integrate them into the current repo. Fetch (read-only display), diff (impact analysis, no edits), status (applied versions), and apply (full integrate pipeline, explicit user intent only). Use when: 'new cc version', 'what changed in claude code', 'apply changelog', a new CC release is mentioned, or the user pastes changelog text.
melodic-software/claude-code-plugins · ★ 13 · AI & Automation · score 73

Install: claude install-skill melodic-software/claude-code-plugins

## 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: - `/claude-ops: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**. `/claude-ops:changelog apply v2.1.152` fetches that version from `code.claude.com/docs/en/changelog.md` 3. **Auto-detect latest**. `/claude-ops: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