oliver-kriska/cc-changelog
.claude/skills/cc-changelog/SKILL.md
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 --global
skillsauthnpx skillsauth add oliver-kriska/claude-elixir-phoenix cc-changelogInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 7, 2026, 8:07 PM8.2s2 files scanned
SKILL.md
- name:
- cc-changelog
- description:
- |
- 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
/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 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 scripts/fetch-cc-changelog.sh --all
For --set=X: run bash 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 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
Related Skills
oliver-kriska/freeze
tools
VerifiedTrustedCommunity
Scope or freeze which files Claude can edit during debugging, a refactor, or review. Use when edits should stay in specific dirs, or for a read-only investigate lock. Backed by a sentinel + PreToolUse hook.
425SKILL.mdUpdated Jun 9, 2026
oliver-kriska/ash-framework
development
VerifiedTrustedCommunity
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
425SKILL.mdUpdated Jun 9, 2026
oliver-kriska/phx:mix-compression
development
VerifiedTrustedCommunity
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
425SKILL.mdUpdated May 13, 2026
oliver-kriska/narrow-bare-rescue
development
VerifiedTrustedCommunity
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
425SKILL.mdUpdated Apr 25, 2026