What problem does it solve?
Release notes often get written late or contain inaccurate summaries, because they are based on incomplete PR information instead of a full review of merged changes.
Core Features & Use Cases
- Versioned release note generation: Creates release notes for a specific target version from changes merged since the previous release tag.
- PR investigation and structured summarization: Collects PR numbers, dates, titles, bodies, labels, and related files, then produces both PR summaries and user-facing release notes.
- Upstream model-change verification: When the upstream mulmocast package is updated, diffs actual code to distinguish models that are truly new versus those already present in the prior version.
- Clear user vs developer impact categorization: Separates user-visible fixes and improvements from developer-only/internal changes for appropriate sections.
Quick Start
Generate the release notes by providing the target version number (for example, 1.0.11) and letting the skill compile PR summaries and user-facing notes into docs/release_notes/v1.0.11/.