Draft release notes from changes

---
name: "aboutcodex-release-notes"
description: "Turn verified code changes into clear release notes for users and maintainers. Use when the user asks for a changelog, release summary, or upgrade notes from a diff or release."
---

# Draft release notes from changes

Turn verified code changes into clear release notes for users and maintainers.

## Workflow

1. Establish the release boundary from tags, commits, or the supplied change set.
2. Group changes by user outcome: added, changed, fixed, deprecated, or removed.
3. Describe observable behavior and migration steps; omit internal refactors with no useful reader impact.
4. Verify version numbers, links, compatibility statements, and breaking changes against project evidence.
5. Write a short public summary and a fuller maintainer section when both audiences need it.

Read `references/NOTES.md` before finalizing the work. Follow project instructions and the user's authorized scope. Use available evidence, label assumptions, and never report a check as passing unless it actually ran.

## Deliverable

Accurate, audience-appropriate release notes grounded in the actual changes. State material limitations and link to changed files or rendered evidence when available.