changeloglisted

# Changelog ## When to use Use this skill before a release, or when the CHANGELOG is stale and needs a new section. ## Steps 1. Collect commits since the last tag (`git log <last>..HEAD`). 2. Group them by type: Added, Changed, Fixed, Deprecated, Removed, Security. 3. Turn each into a one-line user-facing note; drop internal/chore noise. 4. Link to PRs or issues where available. 5. Prepend a new `## [version]` heading with the date. ## Examples - "Generate the CHANGELOG for v1.4.0" - "Summarize what changed since the last tag" ## References Follow Keep a Changelog format; write for the reader ("you can now…") not the commit log ("updated X").