# Release Notes

Draft a release note section from a commit range, grouped by what the reader gets.

- Repository: https://github.com/kirodotdev/KiroCrew (4711 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kirodotdev/KiroCrew --skill release-notes -g -a claude-code -y`
Codex: `npx skills add kirodotdev/KiroCrew --skill release-notes -g -a codex -y`
Cursor: `npx skills add kirodotdev/KiroCrew --skill release-notes -g -a cursor -y`
Gemini CLI: `npx skills add kirodotdev/KiroCrew --skill release-notes -g -a gemini-cli -y`

## Description

Draft a release note section from a commit range, grouped by what the reader gets.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# release-notes

## When to use
Asked to draft the changelog section for a version bump.

## Steps
1. Read the commit range and partition it -- account for every commit.
2. Group by what the reader gets, most interesting first. Never by commit type.
3. Lead with breaking changes when the release has any.

## Gotchas
- A list of commit subjects is not a changelog section.
- Never restate a count of commits.