changelog-authoring

Run git log and git diff from the latest tag to HEAD to enumerate changes, then distill each user-visible change into a plain bullet. This Skill automates that process and writes the bullets into the [Unreleased] section of CHANGELOG.md.

Squashed merge commits often hide the real change behind a terse subject line. Fetch the original PR with gh pr view to get its title, description, and author, then distill that into a changelog-style bullet rather than copying the commit subject.

In this workflow the changelog is updated only once per release, when the maintainer explicitly asks. Individual fixes, features, and PR merges land without changelog lines, and the maintainer folds them into the [Unreleased] section later.

Maintain a dedicated CHANGELOG.md in the extension package and include only changes whose UI surfaces are actually mounted by the extension entrypoint. Shared code that the extension never mounts should not produce an entry, since users would report it as a bug.

Automated drafts still require maintainer judgment: internal refactors without user-visible effects should be omitted, highlights must be genuinely headline-worthy, and entries unsupported by inspected evidence should be dropped rather than guessed.