JulienLerosty/claude-code-team-kit

Write release notes

1. Find the range: git describe --tags --abbrev=0 gives the last tag. If there is none, use the whole history.
2. List subjects: git log <last-tag>..HEAD --no-merges --pretty=format:%s.
3. Call the MCP tool group_commits (server team-kit) with those subjects. It returns Markdown grouped by type, with breaking changes first. If the tool is unavailable, group them by hand using the same headings.
4. Rewrite for readers, not committers: one plain sentence per item, user-visible effect first, no ticket noise. Merge duplicates. Keep anything under "Breaking changes" and say what users must do.
5. Output:

## <version> (<YYYY-MM-DD>)

<2-3 sentence highlight paragraph>

<grouped sections>

Never invent changes that are not in the commit list. If a commit is unclear, read its diff (git show <sha> --stat) before describing it. Ask the user for the version number if you cannot infer it.