Cc Changelog Skill for Claude
| 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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill cc-changelogWhat comes with it
5 603 bytes besides the instructionThe instruction itself
8 sections, as written by the authorClaude 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
/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 "${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:
## 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.mdwith 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
Other skills for the same job
different authors, same section of the catalogue
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
How to use it
Take oliver-kriska/cc-changelog from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.