changelog-update

Automate CHANGELOG.md updates by parsing the existing file or creating a template if missing, then adding entries under the [Unreleased] section by type such as Added or Fixed. This standardizes release logs and reduces formatting drift.

Move unreleased changelog entries to a versioned release by promoting the [Unreleased] section to a specific version number, which automatically updates versioned sections and generates comparison links. This ensures accurate release tracking.

The Keep a Changelog format structures release logs into categorized sections like Added, Changed, Deprecated, Removed, Fixed, and Security under an [Unreleased] header and dated version headers. It provides a consistent standard for tracking project changes.

You do not need an existing CHANGELOG.md file to start adding release entries. The Skill reads for an existing file and automatically creates a properly formatted Keep a Changelog template if one is missing.

You can use interactive mode to guide changelog versioning step by step, prompting for missing details and providing guidance during the update process. This helps maintain accurate entries when information is incomplete.

The best way to validate CHANGELOG formatting against Keep a Changelog standards is to use an automated update tool that reads the file, checks section structure, and verifies comparison links. This catches drift and reduces release risk.