changelog-generator

<!-- Source (originally): https://github.com/ComposioHQ/awesome-claude-skills/blob/master/changelog-generator/SKILL.md Vendored + heavily Rove-overridden. As of the Changesets migration (docs/RELEASING.md) Rove no longer hand-edits a `## [Unreleased]` section — pending notes live as `.changeset/*.md` files and `changeset version` generates the CHANGELOG at release time. The Rove section below takes precedence over anything generic. --> # Changelog Generator (Rove) Drafts release notes as **Changesets** — one `.changeset/<name>.md` file per change — in Rove's house style. `scripts/release.sh` (via `changeset version`) later consumes them into [`packages/kobe/CHANGELOG.md`](../../../packages/kobe/CHANGELOG.md) and the GitHub release body. See [`docs/RELEASING.md`](../../../docs/RELEASING.md) for the full flow. ## When to use - The user says "draft changelog", "write release notes", "add a changeset", "what changed since v0.X.Y", or similar. - After landing a user-facing change that has no changeset yet (e.g. it was committed before this skill existed, or in a batch that skipped them). - Before cutting a release tag — to backfill changesets for anything user-facing that slipped through, so the generated notes are complete. ## Rove project conventions (load-bearing) Every rule in this section overrides the generic guidance further down. ### File format — a changeset, not a CHANGELOG edit - Do **not** hand-edit `packages/kobe/CHANGELOG.md` or invent a `## [Unreleased]` sec...