Skip to content

commandGit and releases

Changelog Entry

Builds a Keep a Changelog entry from the commits since the last tag and adds it to CHANGELOG.md after you approve the text.

npx workspacetemplates add changelog-entry --tool claude-code

Writes 1 file to .claude/commands/

.claude/commands/changelog-entry.md14 lines · 1.1 KBFile
---
description: Builds a Keep a Changelog entry from the commits since the last tag and adds it to CHANGELOG.md after you approve the text.
argument-hint: "[version number, optional]"
---

Draft a changelog entry. Version requested: $ARGUMENTS (suggest one if empty).

1. Find the last tag with `git describe --tags --abbrev=0`. If none exists, use the first commit. List `git log <tag>..HEAD --no-merges` and read the diff of any commit whose subject is unclear.
2. Group changes under **Added**, **Changed**, **Deprecated**, **Removed**, **Fixed**, **Security**. Omit empty groups.
3. Write each line from the user's point of view, in the past tense, one sentence, with the pull request or issue number if the commit has one. Skip refactors, tests, CI and formatting unless users notice.
4. Suggest the version: major for a breaking change, minor for Added, patch otherwise. Explain the choice in one line.
5. Use the heading `## [x.y.z] - YYYY-MM-DD` with today's date, and keep the style of the existing CHANGELOG.md.

Show the entry and ask for approval. Only then insert it below the Unreleased heading. Never create the tag.

What it does

A changelog is for people who use the software, yet raw commit logs are written for the people who build it. This command reads the commits since the latest tag and turns them into entries a user can understand.

It sorts them under the Keep a Changelog headings, drops noise such as formatting and dependency bumps, and suggests the next version number from the kind of changes found.

Example

you › /changelog-entry

agent › ## [2.4.0] - 2026-11-15
### Added
- CSV export on the reports page (#312)
### Fixed
- Login no longer loops when cookies are blocked (#318)

Suggested 2.4.0: one new feature, no breaking change. Add this to CHANGELOG.md?

Questions

Does it create the git tag?
No. It only edits CHANGELOG.md, and only after you approve the text.
What if my commits are messy?
It reads the diffs behind unclear subjects, so the entry reflects what changed.
  • Branch Cleanup

    CommandGit and releases

    Free
  • Cherry Pick Fix

    CommandGit and releases

    Free
  • Commit Message

    CommandGit and releases

    Free
  • Fixup Commits

    CommandGit and releases

    Free