Generate release notes from git history, pull request descriptions, and changelog entries. Use when preparing a release, summarizing changes for stakeholders, or updating a CHANGELOG file.
Installation
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Generate release notes from git history, pull request descriptions, and changelog entries. Use when preparing a release, summarizing changes for stakeholders, or updating a CHANGELOG file.
Drafting Release Notes
Generate clear, audience-appropriate release notes by analyzing the changes between two reference points (tags, branches, or commits).
Process
Gather changes — collect commits, merged PRs, and closed issues between the two reference points.
Categorize — group changes into standard sections:
Added — new features or capabilities
Changed — modifications to existing behavior
Fixed — bug fixes
Removed — deprecated features that were deleted
Security — vulnerability patches or security improvements
Infrastructure — CI/CD, build, or dependency changes
Summarize each entry — write one concise line per change that describes the user-facing impact, not the implementation detail. Reference the PR or issue number.
Highlight breaking changes — call out anything that requires user action (API changes, config format changes, removed features) in a dedicated section at the top.
Add context — include upgrade instructions for breaking changes and link to relevant documentation or migration guides.
