custom-changelog

To generate a Keep a Changelog compliant changelog, use this skill to automatically create a CHANGELOG.md file with standardized sections for Added, Changed, Deprecated, Removed, Fixed, and Security at your project root.

Maintaining release notes with semantic versioning is streamlined by automatically organizing version bumps and unreleased changes into structured Markdown headings with proper dates and version links.

Yes, you can use HISTORY.md or NEWS.md instead of CHANGELOG.md. The skill recognizes these alternative standard Markdown filenames at the project root to enforce consistent changelog formatting.

To add a new release entry, the skill automates moving items from the Unreleased section into a newly published semantic version section, ensuring correct dates and structural compliance.

No specific dependencies or components are required. You only need standard Markdown files named CHANGELOG.md, HISTORY.md, or NEWS.md at your project root and adherence to semantic versioning.

Using the Keep a Changelog v1.1.0 format ensures your documentation remains human-friendly and consistent by enforcing standardized categories like Added, Changed, Fixed, and Security across all project releases.