generate-release-notes

To generate release notes from git history, this Skill analyzes commits, tags, and PRs since the latest tag, then formats the output into categorized markdown sections with contributor kudos and emoji status icons.

Categorizing changelog entries by runtime, frontend, and Docker changes is done by checking file diffs across documented project paths and mapping them to the correct emoji-based markdown sections for each specific area.

The best way to format markdown release notes with consistent emoji sections is to apply established iconography rules that map changes to specific categories like Runtime, Challenges, and Bugfixes, complete with status flags and disclaimer triggers.

Yes, you can automatically attribute contributor kudos and PR references in your changelog by extracting contributor information and commit data from the git history range between the latest tag and HEAD.

Generating release notes requires a git-based project setup with tag and commit history, PR discovery, and trackable file diffs across documented project paths like runtime, dependencies, config, challenges, UI, and i18n.

You should add breaking change disclaimers to release notes when the git history analysis detects policy-relevant updates or breaking changes that trigger the required ⚡, ⚠️, or 📜 status icons and disclaimer flags.