release-bump-changelog

What problem does it solve?

Release workflows often separate marketing copy, GitHub-generated notes, and version tags, which leads to mismatched changelogs, scattered release context, and manual synchronization. This Skill consolidates those steps into a single, repeatable workflow so release narratives and machine-generated notes land together in CHANGELOG.md and the release commit.

Core Features & Use Cases

• Synchronized Release Commit: Generates a launch-style marketing story from the actual change set and ensures the generated GitHub release notes are upserted into CHANGELOG.md alongside the version bump.
• Automated Tagging and Notes: Invokes the repository's cargo bump / release-tag script to generate GitHub-native release notes and create the annotated tag in one operation.
• Use Case: Maintainers preparing a patch, minor, or major release who need consistent marketing copy, accurate GitHub notes, and an auditable changelog entry in a single commit.

Quick Start

Draft a concise marketing paragraph summarizing why the release matters and invoke cargo bump with that marketing copy file so the tag, generated GitHub notes, and CHANGELOG.md are created together.