Cc Changelog

Community

oliver-kriska

cc-changelog

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.

Overview

Publisher	oliver-kriska
Repository	`claude-elixir-phoenix`
Skill name	`cc-changelog`
Stars	565
Forks	45
Bundled files	1
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by oliver-kriska on GitHub. Read the source before you install it.

Installation

Install the Cc Changelog AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/cc-changelog
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/cc-changelog

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git /tmp/claude-elixir-phoenix
mkdir -p .claude/skills
cp -r /tmp/claude-elixir-phoenix/.claude/skills/cc-changelog .claude/skills/cc-changelog

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cc Changelog in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cc Changelog on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cc Changelog is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

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

Iron Laws

ALWAYS fetch before analyzing — never analyze stale cache
NEVER auto-update state — user must confirm after reviewing report
ALWAYS cross-reference plugin files — don't just summarize, map to impact
BREAKING changes are BLOCKERS — surface first, prominently
Track the audit version — state file is the source of truth

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/analysis-rules.md6 KB

Frequently asked questions

What does the Cc Changelog AI skill do?

Why use Cc Changelog on TypingMind?

Because you install it once and use it with any model. Cc Changelog is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cc Changelog in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/cc-changelog. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Cc Changelog?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cc Changelog?

As many as you like. As long as a model supports skills, you can use Cc Changelog with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cc Changelog AI skill free?

Yes. It is published on GitHub by oliver-kriska under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Pinecone

NousResearch

OrganizationPopular

Managed vector DB for production RAG and search.

Qdrant

Vector search engine for production RAG systems.

Tensorrt Llm

High-throughput LLM inference on NVIDIA GPUs.

Internal Comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Claude Code Changelog Assistant

Usage

Execution Flow

Step 1: Fetch & Extract New Entries

Step 2: Analyze Impact

Step 3: Generate Report

Step 4: Update State

Iron Laws

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now