release-changelog

To automatically generate a changelog from git commit history, this Skill parses your repository state and aggregates commit messages, PR summaries, and change notes into a standardized document. It structures the output into clear sections for breaking changes, fixes, and improvements.

Compiling release notes from merged PRs is best handled by aggregating PR summaries and change files into a structured changelog. This process ensures your release documentation accurately captures all project updates and communicates them transparently to users and stakeholders.

Yes, you can format release notes into standardized sections for breaking changes, improvements, fixes, and contributors. This Skill applies preset formatting rules to your parsed git history and PR data to produce a consistent, structured changelog file for stable releases.

Yes, this approach works without external dependencies. The Skill relies entirely on internal scripts and references to parse your existing git history, change files, and PR data, requiring no additional packages to produce the final structured changelog document.

You need to generate a structured changelog document when preparing a new software release. It maintains a clear release history, communicates project updates to users, and ensures development transparency by compiling aggregated commit messages and PR summaries into a standardized format.