Turn the commits into release notes

Claude Code reads the commits since the last tag and writes notes a user could understand.

Release notes grouped by what changed for a user, with internal chores kept separate.

1. 1

   Name the range

   Point Claude Code at the last tag, or paste `git log` if you want a narrower slice.

2. 2

   Separate chores

   Move refactors and dependency bumps into Internal. Users should not have to read them.

3. 3

   Publish the user section

   Use the user-facing lines in the changelog. Keep the internal lines for the team.

Write release notes for the commits since the last tag. Read the commits and the diff. Do not invent features that are not in the history.

Group them as:
- Changes a user would notice
- Fixes
- Internal work, one line each

Each user-facing line names the behavior, not the file. If a commit message is vague, look at the diff and say what changed, or mark the line as unclear. Keep the whole note under 250 words.

Commit messages lie. The notes should follow the diff when the two disagree.

Sample case written by Hidden Logic Lab. Not affiliated with Claude Code.