Skip to content

oliver-kriska/claude-elixir-phoenix / .claude/skills/cc-changelog

cc-changelog

Verified

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.

FileKindSize
SKILL.mdskill md3.4 KB
references/analysis-rules.mdmarkdown5.6 KB
---
name: cc-changelog
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.
argument-hint: "[--full|--set=VERSION]"
effort: medium
---

# 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

### OPPORTUNITY (new features)
- [version] description → **Use case**: how plugin could benefit
  **Files**: which plugin files to update

### RELEVANT FIX (workaround removal)
- [version] description → **Current workaround**: what we do now
  **Action**: can we simplify?

### DEPRECATION (migration needed)
- [version] description → **We use this in**: file:line
  **Migration**: what to change

### INFO (no action)
- [version] brief summary (collapsed)
```

### Step 4: Update State

After user reviews the report, ask:

> "Update last checked version to {latest}? This also updates the
> CC internals memory file. [Yes/No]"

If yes:
1. Run `bash "${CLAUDE_PROJECT_DIR}/scripts/fetch-cc-changelog.sh" --set={latest}`
2. Update memory file `reference_cc_source_internals.md` with new findings
3. If BREAKING or DEPRECATION items found, offer to create a plan

## Iron Laws

1. **ALWAYS fetch before analyzing** — never analyze stale cache
2. **NEVER auto-update state** — user must confirm after reviewing report
3. **ALWAYS cross-reference plugin files** — don't just summarize, map to impact
4. **BREAKING changes are BLOCKERS** — surface first, prominently
5. **Track the audit version** — state file is the source of truth
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall