changelog-writer

# Changelog Writer Writes external, end-user-facing changelog entries with personality — modeled on what Slack, Basecamp, Linear, Raycast, and Tumblr do well: voice and confidence first, jokes used sparingly and only in service of the fact, never replacing it. **This skill is for external/end-user changelogs.** If the audience is internal engineering or the changelog needs to double as a searchable technical record (breaking changes, API versioning, migration notes), this tone is the wrong trade — use a precise, Stripe-style format instead and skip this skill. **Reference files:** - `references/voice-examples.md` — annotated examples of the tone done well (Slack, Basecamp, Tumblr, Raycast, Linear) and done badly, for calibration - `references/draft-format.md` — the full spec for the intermediate draft format the scripts parse **Scripts** (in `scripts/`) — run these against every draft before presenting a final version: - `check-all.mjs` — runs everything below and gives one pass/fail report - `check-structure.mjs`, `check-sass-budget.mjs`, `check-voice.mjs`, `check-length.mjs`, `check-cadence.mjs` --- ## Workflow 1. **Gather the raw material.** Get the list of what actually shipped — feature names, what changed, any tickets/PRs. If it's vague ("we improved search"), ask what specifically changed before writing anything. A joke can't rescue an entry with no real content behind it. 2. **Group by theme, not by ticket.** Five related tweaks become one entry. Assign...