update-changelog

To automate changelog updates, this skill consolidates unreleased git commits since the latest tag into the Unreleased section of your changelog. It uses standard git tooling to detect the baseline version and aggregate the log entries.

You can collect unreleased commits for release notes by running git log with the range from your latest tag to HEAD. This skill automatically determines that baseline tag using git describe and compiles the entries into the changelog.

Yes, updating an existing CHANGELOG.md preserves your current formatting. The skill parses the file, adds concise entries per new change under the Unreleased section, and commits the modifications without breaking the original structure.

Yes, this changelog automation is designed for software teams managing releases with conventional commits and tag-based baselines. It scriptably aggregates those structured commit messages directly into the release notes.

If your repository is missing a CHANGELOG file, the skill will create one. It checks for CHANGELOG.md or CHANGELOG, and if absent, initializes the file to ensure new unreleased entries have a proper destination.

You should not use automated release notes generation if your project lacks git tags or a tag-based baseline, as the skill relies on git describe to find the most recent tag for determining the commit collection starting point.