release-notes

# Release Notes — Poracode Turn a release's PRs, complete commit range, and actual code diff into a **curated, human-readable changelog entry** that reads like a person wrote it — and keep every release in the changelog consistent in voice, shape, and length. Poracode's changelog is **curated data**, not auto-generated. GitHub already auto-lists merged PRs on the Release page; this skill produces the _hand-written_ layer that ships inside the app (Settings → Changelog, the "What's New" dialog) and on the marketing site. ## When to use - The user asks to **add/write release notes**, **update the changelog**, or **"do the changelog for vX.Y.Z"**. - A release was just tagged/published and the in-app + website changelog need an entry. - Backfilling missing releases into the changelog. ## When NOT to use - Editing the _mechanics_ of the changelog feature (the React surfaces, the seen-state gate) — that's normal code work, not this skill. - Writing a single commit message or a GitHub Release body (GitHub generates that). ## The one file you edit There is a **single source of truth**: **`website/public/changelog.json`** on master. The marketing site serves it at `https://www.poracodeapp.com/changelog.json` and the desktop app fetches + caches it at runtime, so editing this one file (and pushing to master, which redeploys the site) updates both surfaces **without an app rebuild**. Shape — an object with a newest-first `releases` array (do not invent fields): ```json { "re...