Version history: Changelog writing skill
v1
scan: pass2026-08-11 — Initial versionInitial version.
v2
currentscan: pass2026-08-13 — First-party content refresh--- name: changelog-writing description: Draft user-facing changelog entries from merged PR titles and descriptions. --- # Changelog writing ## When to use The user asks for a changelog, release notes, or "what shipped" summary. ## Steps - 1. Collect merged PR titles and descriptions for the release window. - 2. Group by: Added, Changed, Fixed, Removed. - 3. Rewrite each entry for end users: outcome first, no internal jargon, - no ticket numbers, present tense. - 4. Flag breaking changes at the top with a migration hint.+ 1. Collect merged PR titles and descriptions for the release window. Ignore + internal-only chores (dependency bumps with no user effect, CI tweaks). + 2. Group remaining changes: Added, Changed, Fixed, Removed. + 3. Rewrite each bullet for an end user: outcome first, present tense, no ticket + numbers, no jargon that is not already in the product UI. + 4. Put breaking changes at the top with a one-line migration hint. - ## Output format+ ## Output - Markdown with a version heading, grouped sections, one bullet per change.+ ```markdown + ## vX.Y.Z — YYYY-MM-DD + + ### Breaking + - … + + ### Added + - … + + ### Changed + - … + + ### Fixed + - … + ``` + + If a section is empty, omit it. Prefer 5–12 bullets over a wall of text.