release-notes

To generate release notes from commit history, you provide the base version, target version, release report, and commit log. The skill processes this structured diff data to output standardized documentation with sections like Summary, What's New, and Breaking Changes.

The best way to structure release notes for different audiences is to apply a predefined template. This skill enforces a defined output structure with sections like Summary, Improvements & Refactors, Operational Notes, and Known Risks to maintain consistent formatting across internal and public documentation.

Yes, you can use a commit log and release diff to create documentation that includes breaking changes and rollback guidance. The skill processes your commit history to produce comprehensive release notes with optional migration steps for your target version.

This release notes generator requires structured inputs including base_version, target_version, release_report, and commit_log. It processes these specific data points against templated structures to produce consistent documentation without needing external dependencies.

Generating release notes from a structured release diff includes sections for Summary, What's New, Improvements & Refactors, Breaking Changes, Operational Notes, Known Risks, and a summarized Commits Included list derived from your commit history.