github-release
Create a GitHub release with auto-generated release notes from commits since the last tag. Uses conventional commits to categorize changes into Features, Bug Fixes, and maintenance sections.
When & Why to Use This Skill
This Claude skill automates the end-to-end GitHub release process by generating professional, structured release notes directly from git commit history. By leveraging conventional commit standards, it intelligently categorizes changes into Features, Bug Fixes, and Maintenance sections, ensuring a consistent and transparent versioning workflow for developers and teams.
Use Cases
- Automated Changelog Generation: Automatically parse git logs since the last tag to create formatted markdown release notes, eliminating manual documentation effort.
- Standardized Release Management: Enforce a consistent release workflow that includes version bumping, commit verification, and GitHub CLI integration for publishing.
- Project Transparency: Provide stakeholders with clear, categorized summaries of 'What's New' and 'Under the Hood' changes for every software iteration.
- DevOps Workflow Optimization: Streamline the transition from code completion to public release by automating the final steps of the delivery pipeline.
| name | github-release |
|---|---|
| description | Create a GitHub release with auto-generated release notes from commits since the last tag. Uses conventional commits to categorize changes into Features, Bug Fixes, and maintenance sections. |
GitHub Release
Create GitHub release with formatted notes from commits since last tag.
Prereqs: gh authenticated, existing tags in repo
Workflow
Get commits since latest tag (run as separate commands):
# First: get latest tag git tag --sort=-v:refname | head -1# Then: get commits since that tag (replace <TAG> with result above) git log <TAG>..HEAD --pretty=format:"%h %s%n%b---" --no-mergesBump version if needed:
- Check if version in
decentpaste-app/src-tauri/tauri.conf.jsonmatches latest tag - If yes, run
/bump-versionskill first - If already bumped, continue
- Check if version in
Categorize by conventional commit prefix:
Prefix Section feat:Features & Improvements fix:Bug Fixes chore:,docs:,refactor:,perf:,style:,test:Under the Hood Generate notes (omit empty sections):
## What's New in vX.X.X [1-2 sentence summary] ### Features & Improvements - **Feature** - Description ### Bug Fixes - **Fix** - Description ### Under the Hood - **Change** - Description ### Downloads | Platform | Download | |----------|----------| | Windows | `DecentPaste_X.X.X_x64-setup.exe` | | macOS (Intel) | `DecentPaste_X.X.X_x64.dmg` | | macOS (Apple Silicon) | `DecentPaste_X.X.X_aarch64.dmg` | | Linux (Debian/Ubuntu) | `DecentPaste_X.X.X_amd64.deb` | | Linux (AppImage) | `DecentPaste_X.X.X_amd64.AppImage` | | Android | `DecentPaste_X.X.X.apk` | --- **Full Changelog**: https://github.com/decentpaste/decentpaste/compare/<prev-tag>...v<version>Confirm with user: show version, tag, commit count, notes preview
Commit and push version bump (CRITICAL - must happen before creating release!):
git add -A && git commit -m "chore: bump version to X.X.X" git push⚠️ CI/CD builds from the pushed code. If you create the release before pushing, CI will build the old version!
Create release:
gh release create vX.X.X --title "DecentPaste vX.X.X" --notes "$(cat <<'EOF' <notes> EOF )"Done: Show release URL, CI will automatically build and upload artifacts