changeloglisted

## Pre-computed context - Read marker (no fetch): !`bash "${CLAUDE_PLUGIN_ROOT}/skills/changelog/scripts/changelog-status.sh" --no-fetch 2>/dev/null | head -4 || echo "(status script unavailable)"` ## Variables Arguments: `$ARGUMENTS` ## Scope Ingests Claude Code changelog entries and integrates them into the repo. Covers the full arc: read upstream changes → orient on repo impact → research new features → triage with user → plan edits → implement → verify → close matching issues. Distinct from: - `/claude-ops:known-issues`. Tracks CC bugs/workarounds. This skill integrates CC feature changes into repo config/docs - Any release-triage automation the consumer runs (issue filing per release). This skill IMPLEMENTS changes, holistically across a release ## Input modes and range Three ways to provide changelog content (priority order): 1. **User pastes text**. Skill parses inline changelog from conversation context; the releases the pasted text names are the range, so the cap and the version check apply to them and not to the repository's default feed 2. **Explicit range or version**. `/claude-ops:changelog diff v2.1.257..v2.1.263` covers both ends inclusive; `apply v2.1.263` covers that one release 3. **Default range**. `/claude-ops:changelog diff` (no range) runs from the read marker to the newest published release The read marker, the default range, and the replay cap are defined in [context/read-actions.md](context/read-actions.md) and computed by `scripts/changelo