Recording Changes

This skill applies Keep a Changelog 2.0.0 to reading, writing, and releasing a project's CHANGELOG.md. The guiding principle behind every rule here: machines can draft, but humans curate.

When to Use

• Reading a CHANGELOG.md to answer what changed in a project or a version.
• Adding an entry for a change just made.
• Creating a CHANGELOG.md for a project that does not have one yet.
• Cutting a release: moving Unreleased into a dated version.
• Reviewing a changelog diff before it merges.

When Not to Use