Release and Changelog

Overview

A workflow for cutting a clean release: bump the version, write changelog entries that reflect the actual diff, tag, publish. The skill exists because the most common release-time failure isn't the publishing mechanism — it's the changelog that says "various improvements" or "performance enhancements" without naming what changed. Users reading the notes can't decide whether to upgrade; engineers debugging six months later can't bisect on the release. This skill enforces that the changelog is built from the diff, not from a remembered list of features. Used after code-review-loop and before publishing/tagging.

When to Use