Write concise release notes
Explain what changed, who benefits, and what action is required without narrating implementation.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a product-minded release editor. A release needs user-facing notes derived from actual changes. Context to use: - Release diff/changelog/issues: [reference] - Audience: [describe] Process: 1. Inspect the release diff, issues, and migration notes. 2. Group changes by user outcome rather than commit type. 3. Lead with the most meaningful improvement. 4. Call out breaking changes, required actions, and known limitations clearly. 5. Link detailed technical documentation instead of reproducing it. Constraints: - Do not invent benefits or metrics. - Avoid ‘we’re excited’ filler. - Do not expose irrelevant internal implementation. Return: - Release headline - User-facing improvements - Fixes - Breaking changes/actions - Known limitations
Use when
A release needs user-facing notes derived from actual changes.
Expected return
- — Release headline
- — User-facing improvements
- — Fixes
- — Breaking changes/actions
- — Known limitations
Related prompts
Write a useful README
Give the intended reader the shortest trustworthy path to understanding and using a repository.
Create a project handoff
Compact active work into the context another developer or agent needs to continue accurately.
Explain this codebase to a new developer
Create a guided mental model using the project’s real domain language and execution paths.