release
Merge PR, tag release, and create GitHub release with changelog notes
When & Why to Use This Skill
This Claude skill automates the end-to-end software release lifecycle on GitHub. It streamlines the transition from code completion to production by handling pull request merging, version tagging, and the creation of official GitHub releases with automated changelog integration. By enforcing pre-release checks and standardizing Git commands, it minimizes human error and accelerates the delivery pipeline.
Use Cases
- Automated Release Management: Quickly merge approved pull requests and generate a new version tag (e.g., v1.0.0) to trigger deployment pipelines.
- Changelog Synchronization: Automatically extract relevant updates from CHANGELOG.md to populate GitHub release notes, ensuring users stay informed of new features and bug fixes.
- Safe Deployment Workflows: Use built-in verification steps to ensure all CI checks have passed before merging, preventing unstable code from reaching the main branch.
- Standardized Versioning: Maintain a consistent versioning strategy across development teams by automating the 'git tag' and 'gh release' commands through a unified interface.
| name | release |
|---|---|
| description | Merge PR, tag release, and create GitHub release with changelog notes |
/release - Tag and Publish Release
Purpose
Merge PR, tag release, and create GitHub release with changelog notes.
Prerequisites
- PR exists and all CI checks pass
- You're ready to release (this is not reversible)
Process
Verify PR status
gh pr status gh pr checksStop if checks are failing.
Merge PR
gh pr merge --squash --delete-branchPull main and verify version
git checkout main git pullConfirm version in pyproject.toml matches intended release.
Create and push tag
git tag vX.Y.Z git push origin vX.Y.ZCreate GitHub release
gh release create vX.Y.Z --title "vX.Y.Z" --notes-file <changelog-section>Extract the relevant section from CHANGELOG.md for release notes. Mark as prerelease if appropriate (
--prerelease).
Notes
- CI typically handles PyPI publishing on tag push
- If release fails, delete the tag before retrying:
git tag -d vX.Y.Z git push origin :refs/tags/vX.Y.Z