release-manager

Automate version bumps, changelog generation, and release preparation from git history.

54|21|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/Nhqvu2005/VibeGravityKit --skill release-manager-nhqvu2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-manager
Source: https://github.com/Nhqvu2005/VibeGravityKit/tree/main/VibeGravityKit/.agent/skills/release-manager
Command: npx skills add https://github.com/Nhqvu2005/VibeGravityKit --skill release-manager-nhqvu2005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the tedious process of managing software releases by generating changelogs, bumping version numbers, and preparing release artifacts, eliminating manual effort and potential errors.

Core Features & Use Cases

  • Automated Changelog Generation: Creates human-readable changelogs based on git commit history, categorized by type (features, fixes, chores, etc.).
  • Version Bumping: Manages semantic versioning by automatically updating version numbers (patch, minor, major) in a VERSION file.
  • Release Preparation: Streamlines the steps needed to prepare for a new release.
  • Use Case: After merging new features and bug fixes into your main branch, use this Skill to automatically generate an updated changelog and increment the minor version number, preparing your project for a new release.

Quick Start

Use the release manager skill to bump the minor version and generate a changelog.

Frequently Asked Questions about release-manager

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

FAQPage Schema
How do I automate changelog generation from git commit history?

Semantic versioning is managed by automatically incrementing version numbers in a VERSION file. The system identifies commit types to determine whether to bump the patch, minor, or major version, ensuring compliant and automated version tracking.

What do I need to set up before automating software release preparation?

Release preparation requires the git command-line interface and a VERSION file for version tracking. Your project must use git history for commit parsing to successfully generate changelogs and automate the semantic version bumping process.

Can I automatically bump the minor version and prepare a release after merging features?

Automated changelog generation parses your git commit history to create human-readable release notes categorized by features, fixes, and chores. This eliminates manual documentation effort and ensures consistent tracking of project changes across release cycles.

Semantic versioning is managed by automatically incrementing version numbers in a VERSION file. The system identifies commit types to determine whether to bump the patch, minor, or major version, ensuring compliant and automated version tracking.

Release preparation requires the git command-line interface and a VERSION file for version tracking. Your project must use git history for commit parsing to successfully generate changelogs and automate the semantic version bumping process.