name	generate-release-notes
description	Generate release notes for this project in a consistent format from merged commits/PRs. Use when the user asks for release notes, a changelog entry, or "what changed in this release".

Generate Release Notes

Produce release notes from the commits/PRs merged since the last release. Group by change type, keep entries user-facing, and follow the exact template below so every release reads the same way.

Steps

Find the range since the last release tag/version:

git fetch --tags
git log "$(git describe --tags --abbrev=0)"..HEAD --pretty=format:'%s (%h)'

Read the version from package.json and today's date.
Map Conventional Commit types to sections (omit empty sections):
- feat -> Features
- fix -> Bug Fixes
- perf/refactor -> Improvements
- docs/chore/build/ci/test -> Maintenance
- any !/BREAKING CHANGE -> Breaking Changes (list first)
Rewrite each line as a concise, user-facing sentence (not the raw commit). Keep the short hash in parentheses. Drop noise (merge commits, release bumps).

Template

## vX.Y.Z - YYYY-MM-DD

### Breaking Changes

- <only if any>

### Features

- <user-facing description> (<hash>)

### Bug Fixes

- <user-facing description> (<hash>)

### Improvements

- <user-facing description> (<hash>)

### Maintenance

- <user-facing description> (<hash>)

Example

Input commits:

feat(auth): add login with email and password (a1b2c3d)
feat(i18n): add Arabic translations (e4f5g6h)
fix(theme): persist dark mode across reloads (i7j8k9l)
refactor(api): simplify query client setup (m0n1o2p)
chore(deps): bump vite to 7 (q3r4s5t)
chore(release): v1.2.0 [skip ci] (u6v7w8x)

Output:

## v1.2.0 - 2026-06-01

### Features

- Log in with email and password (a1b2c3d)
- Arabic language support (e4f5g6h)

### Bug Fixes

- Dark mode now persists across page reloads (i7j8k9l)

### Improvements

- Simplified React Query client setup (m0n1o2p)

### Maintenance

- Upgraded Vite to v7 (q3r4s5t)

Note: the chore(release) bump commit is intentionally excluded.

Generate Release Notes

Produce release notes from the commits/PRs merged since the last release. Group by change type, keep entries user-facing, and follow the exact template below so every release reads the same way.

Steps

Find the range since the last release tag/version:

git fetch --tags git log "$(git describe --tags --abbrev=0)"..HEAD --pretty=format:'%s (%h)'

Read the version from package.json and today's date.

Map Conventional Commit types to sections (omit empty sections):

feat -> Features
fix -> Bug Fixes
perf/refactor -> Improvements
docs/chore/build/ci/test -> Maintenance
any !/BREAKING CHANGE -> Breaking Changes (list first)

Rewrite each line as a concise, user-facing sentence (not the raw commit). Keep the short hash in parentheses. Drop noise (merge commits, release bumps).

Template

## vX.Y.Z - YYYY-MM-DD ### Breaking Changes - <only if any> ### Features - <user-facing description> (<hash>) ### Bug Fixes - <user-facing description> (<hash>) ### Improvements - <user-facing description> (<hash>) ### Maintenance - <user-facing description> (<hash>)

Example

Input commits:

feat(auth): add login with email and password (a1b2c3d) feat(i18n): add Arabic translations (e4f5g6h) fix(theme): persist dark mode across reloads (i7j8k9l) refactor(api): simplify query client setup (m0n1o2p) chore(deps): bump vite to 7 (q3r4s5t) chore(release): v1.2.0 [skip ci] (u6v7w8x)

Output:

## v1.2.0 - 2026-06-01 ### Features - Log in with email and password (a1b2c3d) - Arabic language support (e4f5g6h) ### Bug Fixes - Dark mode now persists across page reloads (i7j8k9l) ### Improvements - Simplified React Query client setup (m0n1o2p) ### Maintenance - Upgraded Vite to v7 (q3r4s5t)

Note: the chore(release) bump commit is intentionally excluded.

generate-release-notes