Agent skill

Cc Changelog

by oliver-kriska in oliver-kriska/claude-elixir-phoenix

CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check, analyze impact on plugin (breaking changes, opportunities, deprecations).

MITAuto-check passedDevelopment

Install Cc Changelog

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix cc-changelog --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/cc-changelog .claude/skills/cc-changelog && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "cc-changelog" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/cc-changelog into .claude/skills/cc-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cc-changelog", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

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

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix cc-changelog --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/cc-changelog .agents/skills/cc-changelog && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "cc-changelog" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/cc-changelog into .agents/skills/cc-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cc-changelog", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix cc-changelog --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/cc-changelog .cursor/skills/cc-changelog && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "cc-changelog" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/cc-changelog into .cursor/skills/cc-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cc-changelog", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/oliver-kriska/claude-elixir-phoenix.git --path .claude/skills/cc-changelog

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix cc-changelog --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/cc-changelog .gemini/skills/cc-changelog && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "cc-changelog" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/cc-changelog into .gemini/skills/cc-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cc-changelog", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix cc-changelog

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/cc-changelog .github/skills/cc-changelog && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "cc-changelog" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/cc-changelog into .github/skills/cc-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cc-changelog", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix cc-changelog --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/cc-changelog .opencode/skills/cc-changelog && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "cc-changelog" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/cc-changelog into .opencode/skills/cc-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cc-changelog", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: cc-changelog
GitHub stars: 565
Token cost: ~864 tokens
SKILL.md length: 273 words
Files: 2 (incl. references)
Skills in repo: 109
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check, analyze impact on plugin (breaking changes, opportunities, deprecations).

Works in 4 steps: Fetch & Extract New Entries → Analyze Impact → Generate Report → …
Tasks that involve Changelog and release notes
SKILL.md covers Usage, Execution Flow and Iron Laws
Calls bash

What it does

Cc Changelog is an agent skill from oliver-kriska/claude-elixir-phoenix. 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.

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/analysis-rules.md`).

It sits in Development, covering Changelog and release notes. It works with Bash. The repository describes itself as: Claude Code plugin for Elixir/Phoenix/LiveView — 26 specialist agents, Iron Laws enforcement, and Tidewave MCP integration. Plan features with parallel research agents, execute… The licence is MIT.

When your agent uses it

Tasks that involve Changelog and release notes

Example prompts

“/cc-changelog”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Fetch & Extract New Entries
Analyze Impact
Generate Report
Update State

What it can do on your machine

Read from SKILL.md and the folder at commit 9767a82. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cc Changelog loads about 864 tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 273 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~59
When it runs · the whole SKILL.md, loaded when a task matches: ~864
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from oliver-kriska/claude-elixir-phoenix at commit 9767a82, republished under its MIT licence (© oliver-kriska). 273 words, ~864 tokens.

Download SKILL.mdSave it as .claude/skills/cc-changelog/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

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:

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

Files

SKILL.md and 1 other file (references) in .claude/skills/cc-changelog of oliver-kriska/claude-elixir-phoenix.

SKILL.md
references/analysis-rules.md

Open the folder on GitHubat commit 9767a82

Compare with similar skills

Cc Changelog next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cc Changelog compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Cc Changelog this skilloliver-kriska/claude-elixir-phoenix	565	—	~864	Automated safety check: Pass	MIT	5 days ago
Lade Releasezifeo/lade	134	—	~749	Automated safety check: Pass	MPL-2.0	today
Sake CI Releasekattouf/Sake	116	—	~731	Automated safety check: Pass	MIT	6 mo ago
Swpm Releasedeinsoftware/swpm	125	—	~1.1k	Automated safety check: Pass	MIT	4 mo ago
Documentationpromovaweb/setupvibe	103	—	~477	Automated safety check: Pass	GPL-3.0	1 mo ago
Survey SDK AuditPostHog/posthog	40k	—	~4.3k	Automated safety check: Pass	Custom licence	yesterday

Similar skills

Lade Release
zifeo/lade
Prepare a Lade release: update CHANGELOG.md and bump crate versions with cargo set-version.
134 GitHub stars~749 tokensUpdated today
DevelopmentAuto-check passed
Sake CI Release
kattouf/Sake
A skill your agent uses when working on CI workflows, GitHub Actions, release process, changelog generation (git-cliff), or dependabot configuration.
116 GitHub stars~731 tokensUpdated 6 mo ago
DevelopmentAuto-check passed
Swpm Release
deinsoftware/swpm
Automated release bash script for SWPM. An agent skill from deinsoftware/swpm.
125 GitHub stars~1.1k tokensUpdated 4 mo ago
DevelopmentAuto-check passed
Documentation
promovaweb/setupvibe
Workflow mestre para gestão de documentação do SetupVibe. An agent skill from promovaweb/setupvibe.
103 GitHub stars~477 tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Survey SDK Audit
PostHog/posthog
Official
Audit PostHog survey SDK features and version requirements, and implement survey changes across the backend, UI, and SDK repositories.
40k GitHub stars~4.3k tokensUpdated yesterday
DevelopmentAuto-check passed
Make Changelog
promovaweb/setupvibe
Gerencia entradas no CHANGELOG.md seguindo Keep a Changelog.
103 GitHub stars~470 tokensUpdated 1 mo ago
DevelopmentAuto-check passed

Questions about Cc Changelog

What does Cc Changelog do?

CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check, analyze impact on plugin (breaking changes, opportunities, deprecations). Cc Changelog is an agent skill from oliver-kriska/claude-elixir-phoenix. CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check, analyze impact on plugin (breaking changes, opportunities, deprecations).

When should I use Cc Changelog?

Cc Changelog fits situations like: tasks that involve Changelog and release notes.

How do I install Cc Changelog in Claude Code?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -a claude-code`. Or copy the skill folder (.claude/skills/cc-changelog in oliver-kriska/claude-elixir-phoenix) into .claude/skills/cc-changelog in your project. Claude Code loads it when a task matches its description.

How do I install Cc Changelog in Codex?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -a codex`. Or copy the skill folder (.claude/skills/cc-changelog in oliver-kriska/claude-elixir-phoenix) into .agents/skills/cc-changelog in your project. Codex loads it when a task matches its description.

Can I use Cc Changelog in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add oliver-kriska/claude-elixir-phoenix --skill cc-changelog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cc-changelog, .gemini/skills/cc-changelog, .github/skills/cc-changelog and .opencode/skills/cc-changelog in your project.

What does Cc Changelog need to run?

Going by SKILL.md and its folder, Cc Changelog needs the command-line tools its instructions call (bash).

Does Cc Changelog access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cc Changelog safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cc Changelog use?

Cc Changelog is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cc Changelog use?

About 864 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Cc Changelog?

Skills that share tags, products or a category with Cc Changelog: Lade Release (zifeo/lade, 134 stars), Sake CI Release (kattouf/Sake, 116 stars), Swpm Release (deinsoftware/swpm, 125 stars) and Documentation (promovaweb/setupvibe, 103 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cc Changelog?

oliver-kriska (a GitHub user) maintains it in oliver-kriska/claude-elixir-phoenix, which has 565 GitHub stars. The repository holds 109 skills in this directory. The repository was last updated on October 5, 2026.

Source: oliver-kriska/claude-elixir-phoenix on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Cc Changelog

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

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

Files

Compare with similar skills

Similar skills

More from oliver-kriska/claude-elixir-phoenix

Related

Questions about Cc Changelog