cc:changelog

Included with Lifetime

$97 forever

Show recent Claude Code changes personalized to user's setup. Trigger when user asks about changelog, "what's new", "cc changelog", "claude code updates", "recent changes", or wants to know what changed in Claude Code.

AI Agentsscripts

What this skill does


# CC Changelog

Show recent Claude Code changes, scored by relevance to the user's installed skills, commands, plugins, hooks, and usage patterns.

## Workflow

1. Run the data collection script:

```bash
${CLAUDE_SKILL_DIR}/scripts/cc-changelog.ts 2>/dev/null
```

To force a date-based lookback (ignoring lastVersion state), pass `--lookback-days=N`:

```bash
${CLAUDE_SKILL_DIR}/scripts/cc-changelog.ts --lookback-days=14 2>/dev/null
```

Use `--lookback-days` when the user asks for changes from a specific time period (e.g. "last 14 days", "last week" = 7 days).

2. Parse the JSON output and present a **concise, themed** summary:

### Format rules

- **Rank all items, then keep top 50%.** Score each candidate bullet by combined weight (high → low):
  1. Personal relevance — matches user's installed skills, commands, plugins, hooks, usage patterns
  2. User-facing surface changes — visible message/UI text, prompts, output format, defaults the user reads or types
  3. Parameter / flag / config / API / schema changes — anything the user invokes or configures (CLI flags, settings keys, hook events, tool schemas, command args)
  4. New features / capabilities — net-new things user can do
  5. Behavioral changes — different output for same input, removed/changed defaults, breaking changes
  6. Internal / perf / refactor — deprioritize unless user-observable. A perf win that doesn't change behavior or UX ranks low.
     Sort all candidates by this combined score, drop bottom half. Round up on odd counts. Mention dropped count at bottom.
- **Group surviving items by theme, not by version.** Cluster into categories (e.g. "Startup & Performance", "Plugins & Skills", "Agent Teams", "Bash & Permissions").
- **Each item = 1 short line.** Rewrite verbose changelog entries into punchy summaries (5-15 words). Append version+date tag: `(2.1.47, Feb 18)`
- **Lead with a 1-2 sentence TL;DR** of the most impactful changes for this user.
- **Explain WHY it's relevant** by referencing what the user uses. Don't just say "matches: Bash" - say things like "you use hooks" or "affects your StatusLine setup".

```
## Claude Code changelog - {version range} ({date range})

{1-2 sentence TL;DR of biggest changes relevant to user}

### {Theme name}
- {Punchy summary} (2.1.47, Feb 18) — {why it matters to you}
- ...

### {Theme name}
- ...

### System prompt
{Summarize the diff concisely - see rules below}

{N} lower-ranked items skipped. [Full changelog]({url})
```

3. If the `versions` array is empty, say: "You're up to date! No new changes since {currentVersion}." Do NOT advance the watermark.

4. **After presenting results to the user**, advance the watermark so the same changes aren't shown again:

```bash
${CLAUDE_SKILL_DIR}/scripts/cc-changelog-advance.ts 2>/dev/null
```

Only run this AFTER the changelog summary is fully rendered. Never run it if the versions array was empty.

### System prompt diff rules

When `systemPromptDiff.prompt` or `systemPromptDiff.flags` is non-null, summarize the unified diff into actionable bullet points. Categorize changes:

**Prompt changes** - summarize each meaningful hunk as one bullet:

- New sections/blocks added (e.g. "New `currentDate` context block added")
- Instructions changed (e.g. "Auto memory guidelines expanded with what to/not to save")
- Tool schema changes (e.g. "AskUserQuestion got `markdown` preview field")
- Model/version bumps (e.g. "Knowledge cutoff Jan 2025 -> Aug 2025")
- Removed content (e.g. "Agent Teams 'not available' disclaimer removed")

**Flag changes** - list added/removed flags:

- Added: `flag_name`
- Removed: `flag_name`

Skip cosmetic changes (typo fixes, whitespace, path changes in test environments). Focus on behavioral changes that affect how Claude works.

## Notes

- The script handles all data fetching, parsing, and relevance scoring
- State is persisted at `~/.claude/custom-cache/cc-changelog-state.json`
- First run uses a 14-day lookback window; subsequent runs check from last version
- Requires `gh` CLI authenticated with GitHub

Files: 3

Size: 18.6 KB

Complexity: 45/100

Category: AI Agents

Source: https://github.com/lttr/claude-marketplace/tree/main/plugins/cc/skills/changelog

Related in AI Agents

skill-development

Included

Comprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.

AI Agentsscripts

reprompter

Included

Transform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.

AI Agentsscripts

adaptive-compaction

Included

Adaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.

AI Agentsscripts

agent-skill-creator

Included

Create cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.

AI Agentsscripts

llm-wiki

Included

Use when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.

AI Agentsscripts

skill-master

Included

Agent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.

AI Agentsscripts