cc-changelog
Skill573 starsChanged 4 months agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- zeikar/hyperclaudetheir own version, first seen Sep 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- zeikar/hyperclaude★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- codex-abSkill
- docs-checkSkill
- plugin-dev-workflowSkill
- promoteSkill
- releaseSkill
- session-deep-diveSkill
- session-scanSkill
- session-trendsSkill
- skill-monitorSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
If output starts with STATUS: UP_TO_DATE → report "No new CC versions" and stop.
- Very specific: line 35
If STATUS: NEW_VERSIONS → continue with the changelog content below the header.
- Distinctive: line 42
Read the new changelog entries.
- Distinctive: line 84
After user reviews the report, ask:
- Very specific: line 91
Update memory file reference_cc_source_internals.md with new findings
- Distinctive: line 92
If BREAKING or DEPRECATION items found, offer to create a plan
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
/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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

