name	release-description
description	Draft a concise release summary by analyzing commit titles since the last git tag. Use when the user asks to update release notes, prepare a release summary, or summarize changes for a version.

Release Description

Find the latest release tag:
```
git tag --sort=-creatordate | head -1
```
List commit titles since that tag:
```
git log --oneline <tag>..HEAD
```
Categorize commits:

Prefix Category
feat New behavior
fix Bug fixes
perf Performance
refactor Internal cleanup
docs Documentation
chore, build, test Maintenance
Write a concise, user-facing summary:
- One sentence.
- Plain language.
- Mention moderation behavior, provider compatibility, privacy, caching, or publishing only when those changed.
- Do not mention every commit.
If the user wants it written into release materials, update the relevant changelog or GitHub release draft after confirming where it should live.

name	release-description
description	Draft a concise release summary by analyzing commit titles since the last git tag. Use when the user asks to update release notes, prepare a release summary, or summarize changes for a version.

Find the latest release tag:
```
git tag --sort=-creatordate | head -1
```
List commit titles since that tag:
```
git log --oneline <tag>..HEAD
```
Categorize commits:

Prefix Category
feat New behavior
fix Bug fixes
perf Performance
refactor Internal cleanup
docs Documentation
chore, build, test Maintenance
Write a concise, user-facing summary:
- One sentence.
- Plain language.
- Mention moderation behavior, provider compatibility, privacy, caching, or publishing only when those changed.
- Do not mention every commit.
If the user wants it written into release materials, update the relevant changelog or GitHub release draft after confirming where it should live.

release-description