skills.rest
nvimcraft
nvimcraftCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-release

Generate release version recommendations and changelog drafts from Git history.

Updated Feb 7, 2026
Search Tags:#git#changelog#conventional commits#github#release#semver
One-click install
npx skills add https://github.com/nvimcraft/dotfiles-macos --skill git-release-nvimcraft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-release
Source: https://github.com/nvimcraft/dotfiles-macos/tree/main/.config/opencode/skills/git-release
Command: npx skills add https://github.com/nvimcraft/dotfiles-macos --skill git-release-nvimcraft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of analyzing git history and preparing release drafts by turning commits and pull requests into structured versioning recommendations and release notes.

Core Features & Use Cases

  • Semantic Version Analysis: Evaluates conventional commits, breaking changes, and change categories to suggest major, minor, or patch releases.
  • Release Note Generation: Creates GitHub-ready changelogs organized by features, fixes, breaking changes, and maintenance updates.
  • Use Case: Help a maintainer prepare a release draft after a development cycle by analyzing merged work and producing a version recommendation with copy-pasteable release commands.

Quick Start

Ask the git-release skill to analyze the recent commits and generate a release draft with version bump rationale and GitHub release notes.

Frequently Asked Questions about git-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a changelog from conventional commits and merged pull requests?▼

To generate a changelog from conventional commits, the skill analyzes your git history and pull request metadata, categorizing changes into features, fixes, breaking changes, and maintenance updates to produce GitHub-ready release notes.

How do I determine the correct semantic version bump from recent git history?▼

Determining the correct semantic version bump involves evaluating commit patterns and breaking change indicators in your git history. The skill analyzes conventional commits to recommend a major, minor, or patch release.

Can I draft a GitHub release automatically from commit metadata?▼

Yes, you can draft a GitHub release automatically from commit metadata. The skill evaluates merged pull requests and commit patterns to produce a version recommendation with copy-pasteable release commands and formatted notes.

Do I need conventional commits to generate semantic versioning recommendations?▼

Using conventional commits is required to accurately generate semantic versioning recommendations. The skill relies on analyzing conventional commit patterns and breaking change indicators to suggest the correct version bump.

What is the best way to prepare a software release draft after a development cycle?▼

The best way to prepare a software release draft is to analyze merged work from the development cycle. The skill processes git history to produce a structured version bump rationale and GitHub release notes.

What are the limitations of automating release version recommendations from git history?▼

A limitation of automating release version recommendations is that the skill generates drafts and suggestions but includes manual release execution safeguards, meaning a human must still review and execute the final release commands.

Related Skills

Explore More Software Engineering Skills→
ArabelaTsoArabelaTso
142

change-log-generator

Generate Markdown changelogs from git commit history with conventional commits.

Community
Intermediate
NachoOsellaNachoOsella
6

git-release

Determine semantic versions from commits and create GitHub release drafts.

Community
Intermediate
ntk148vntk148v
1

conventional-commits

Generate conventional commit messages with type, scope, and breaking change markers.

Community
Basic
haJ1thaJ1t

auto-changelog

Generate CHANGELOG.md from git commit history using Conventional Commits.

Community
Advanced