# Cc Changelog

CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check, analyze...

- Repository: https://github.com/oliver-kriska/claude-elixir-phoenix (572 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -g -a claude-code -y`
Codex: `npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -g -a codex -y`
Cursor: `npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -g -a cursor -y`
Gemini CLI: `npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add oliver-kriska/claude-elixir-phoenix`

## Description

CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check, analyze impact on plugin (breaking changes, opportunities, deprecations). Run periodically or before releases. NOT part of the distributed plugin.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Claude Code Changelog Assistant

Tracks Claude Code releases against the plugin. Fetches the CC changelog,
extracts entries newer than last check, and analyzes impact on plugin
components (agents, skills, hooks, config).

## Usage

```text
/cc-changelog                  # Check for new CC versions, analyze impact
/cc-changelog --full           # Re-analyze all versions (ignore last check)
/cc-changelog --set=2.1.85     # Reset last checked version (then re-run)
```

## Execution Flow

### Step 1: Fetch & Extract New Entries

```bash
bash "${CLAUDE_PROJECT_DIR}/scripts/fetch-cc-changelog.sh"
```

If output starts with `STATUS: UP_TO_DATE` → report "No new CC versions" and stop.

If `STATUS: NEW_VERSIONS` → continue with the changelog content below the header.

For `--full`: run `bash "${CLAUDE_PROJECT_DIR}/scripts/fetch-cc-changelog.sh" --all`
For `--set=X`: run `bash "${CLAUDE_PROJECT_DIR}/scripts/fetch-cc-changelog.sh" --set=X`, then re-run without flag.

### Step 2: Analyze Impact

Read the new changelog entries. For EACH entry, classify into one of:

| Category | Meaning | Action |
|----------|---------|--------|
| **BREAKING** | May break existing plugin functionality | Immediate fix required |
| **OPPORTUNITY** | New CC feature the plugin could use | Add to backlog/plan |
| **RELEVANT FIX** | CC fixed a bug we worked around | Check if workaround can be removed |
| **DEPRECATION** | CC removing something we use | Plan migration |
| **INFO** | Good to know, no action needed | Log in memory update |

Cross-reference against plugin components using rules in
`${CLAUDE_SKILL_DIR}/references/analysis-rules.md`.

### Step 3: Generate Report

Output a structured report:

```markdown
## CC Changelog Analysis: v{last_checked} → v{latest}

### BREAKING (action required)
- [version] description → **Impact**: which plugin file/component
  **Fix**: specific action needed

The rest: https://github.com/oliver-kriska/claude-elixir-phoenix/blob/HEAD/.claude/skills/cc-changelog/SKILL.md