| name | git-release |
| description | Create consistent releases with changelogs, version bumps, and release notes from git history |
| license | MIT |
| compatibility | opencode |
| metadata | {"audience":"maintainers","workflow":"github"} |
What I do
- Analyze merged PRs and commits since the last release tag
- Draft release notes grouped by category (Features, Fixes, Breaking Changes, etc.)
- Propose a semantic version bump based on commit types
- Generate a copy-pasteable
gh release create command
- Optionally update CHANGELOG.md
When to use me
Use this skill when you are preparing a tagged release.
Ask clarifying questions if the target versioning scheme is unclear.
Process
- Find the latest release tag:
git describe --tags --abbrev=0
- List commits since that tag:
git log <tag>..HEAD --oneline
- Categorize commits by type (feat, fix, breaking, chore, docs)
- Determine version bump:
- BREAKING CHANGE or
! suffix -> Major
feat: -> Minor
fix: -> Patch
- Draft release notes in this format:
## [vX.Y.Z] - YYYY-MM-DD
### Breaking Changes
- Description (#PR)
### Features
- Description (#PR)
### Bug Fixes
- Description (#PR)
### Other
- Description (#PR)
- Provide the release command:
gh release create vX.Y.Z --title "vX.Y.Z" --notes-file release-notes.md
Conventions