changelog-generator

To generate release notes from git commit history, the skill scans commits between versions or over a date range and transforms them into structured markdown. It parses the raw commit data and groups changes into categories like features, improvements, and fixes.

Yes, you can automatically group commit changes into categories for a changelog. The skill categorizes parsed git history into features, improvements, fixes, and breaking changes before formatting the output into a structured, publish-ready markdown document.

The best way to create customer-facing changelogs from recent software commits is using narrative generation. The skill applies a defined style guide to format categorized git history into polished, user-facing markdown summaries suitable for weekly or monthly release updates.

The changelog generator parses standard git commit history between versions or over date ranges. While it categorizes changes into features, fixes, and improvements, the metadata does not specify a strict prerequisite commit message format for generating the structured markdown output.

To create a markdown summary of a sprint's development updates, the skill gathers commits from the specified date range and categorizes them. It then generates a concise, narrative-formatted changelog document summarizing the sprint's software changes for product teams.