draft-release-notes

You can automate release notes generation by analyzing merged pull requests and internal issue context to produce professional, user-facing changelog entries. This process requires GitHub CLI integration and access to repository commit history to verify and link all user-observable changes.

The best way to summarize internal PR titles is by leveraging Linear issue context to transform opaque development details into clear, user-facing release notes without verbatim copying. This ensures consistent documentation of features, fixes, and breaking changes.

Automated changelog formatting handles breaking changes by applying standardized categorization that correctly highlights breaking changes and migration recipes. It automatically generates categorized release notes and updates the project changelog for the upcoming stable version.

Yes, you need GitHub CLI integration and access to repository commit history to generate stable release notes. These prerequisites allow the system to verify and link all user-observable changes while filtering out development and beta noise from the final documentation.

Yes, you can filter out beta and development noise when cutting stable release notes. The automated PR enumeration identifies all merged changes since the last stable release tag while excluding this noise to ensure only user-observable changes are documented.

You should invoke the draft-release-notes skill while in the release branch to generate the release notes file and update the changelog for the upcoming stable version. This applies to the stable release-cutting workflow to ensure consistent documentation.