Release Notes

You can generate release notes automatically by providing completed task records, PR summaries, and a release manifest. The skill parses these inputs to produce structured documentation covering features, fixes, and improvements for a specified version.

Yes, the release notes generator produces a Keep a Changelog–compliant changelog entry alongside the main release notes and a known issues list, ensuring your documentation follows standard formatting conventions for version tracking.

Yes, you can tailor release notes for different audiences by specifying internal, external, or both in the audience input. This ensures the generated documentation meets the specific informational needs of each stakeholder group.

The changelog generation process gracefully handles missing git history data by validating available inputs like the version and changelog paths, synthesizing release notes from existing task completion records and PR summaries instead.

The best way to structure known issues is to separate them into a dedicated list within your release documentation. This skill automatically parses resolved and unresolved issues from your release cycle to generate a distinct known issues section.

You need a release manifest along with tasks and PR summaries to generate stakeholder-friendly release notes. The process validates the version and changelog paths from these inputs to accurately categorize features, fixes, and improvements.