agentsclimarketplace

Cc changelog

Skill slbug/claude-ruby-grape-rails/.claude/skills/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.From its SKILL.md

Install
npx -y skills add slbug/claude-ruby-grape-rails --skill cc-changelog

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.3 KB, as published. Nobody here has run it

Claude Code Changelog Assistant

Audience: Agents, Not Humans

Imperative-only. Tables for category and shape lists.

Usage

CommandPurpose
/cc-changelogcheck for new CC versions, analyze impact
/cc-changelog --allre-analyze all versions (ignore last check)
/cc-changelog --set=<version>reset last checked version, then re-run

Execution Flow

Step 1: Fetch New Entries

From repo root: bash ./scripts/fetch-cc-changelog.sh (or --all for full re-fetch).

Output prefixAction
STATUS: UP_TO_DATEreport "No new CC versions" and stop
STATUS: NEW_VERSIONScontinue with content below the header

--all flag → bash ./scripts/fetch-cc-changelog.sh --all. --set=X flag → bash ./scripts/fetch-cc-changelog.sh --set=X, then re-run without flag.

Step 2: Analyze Impact

Read new changelog entries. Classify each into one category:

CategoryMeaningAction
BREAKINGmay break existing plugin functionalityimmediate fix required
OPPORTUNITYnew CC feature plugin could useadd to backlog/plan
RELEVANT FIXCC fixed a bug we worked aroundcheck if workaround removable
DEPRECATIONCC removing something we useplan migration
INFOgood to know, no action neededlog only

Cross-reference plugin components via ${CLAUDE_SKILL_DIR}/references/analysis-rules.md.

Step 3: Generate Report

Output 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}? [Yes/No]"

If yes: run bash ./scripts/fetch-cc-changelog.sh --set={latest}.

If BREAKING or DEPRECATION found, offer to create a plan.

Iron Laws

  1. ALWAYS fetch before analyzing — never analyze stale cache.
  2. NEVER auto-update state — user confirms after reviewing report.
  3. ALWAYS cross-reference plugin files — map impact, not just summarize.
  4. BREAKING changes are BLOCKERS — surface first, prominently.
  5. State file is the source of truth for audit version.

Epistemic Posture

Direct language for breaking-change analysis. CC version that removes or renames a plugin API the repo uses → label BLOCKER without softening. Deprecations labeled deprecated in the CC changelog → direct flag, not "consider migrating eventually". No apology cascades, no hedge chains.

Keep looking

Skills are one crate of 610,677. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.