changelog

# 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. Ro...