release

Name: release
Availability: InStock
Author: lklimek

Automate software releases with version bumping, changelog generation, and GitHub releases.

Updated Mar 5, 2026

Search Tags:#automation #changelog #versioning #github #release #semver

Ready to run

npx skills add https://github.com/lklimek/memcan --skill release-lklimek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/lklimek/memcan/tree/main/.claude/skills/release
Command: npx skills add https://github.com/lklimek/memcan --skill release-lklimek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the complex and error-prone process of releasing new software versions, ensuring consistency and reducing manual effort.

Core Features & Use Cases

Automated Version Bumping: Intelligently determines the next version number (major, minor, patch) based on commit history and code changes.
Changelog Generation: Creates a human-readable changelog following the Keep a Changelog standard.
Commit & Push: Commits version updates and pushes changes to the remote repository.
GitHub Release Creation: Publishes a new release on GitHub with the generated changelog.
Use Case: After merging a new feature, you can invoke this skill to automatically handle the versioning, changelog update, and GitHub release, allowing you to focus on development.

Quick Start

Run the release skill to automatically determine the next version and create a new release.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate software releases with SemVer version bumping and changelog generation?▼

Automated software release tools analyze git history and code diffs to determine SemVer increments, generate Keep a Changelog formatted notes, commit changes, and push to GitHub. This streamlines the entire release process by evaluating commit history to decide whether a major, minor, or patch version bump is required.

Do I need GitHub CLI and Cargo to automate version management and publishing?▼

Yes, automating version management and publishing requires git, GitHub CLI, and Cargo. GitHub CLI is needed to create the GitHub release, while Cargo handles the version management and publishing aspects for your software project.

How does automated changelog generation work with Keep a Changelog standards?▼

Automated changelog generation works by analyzing git history and code diffs to produce human-readable release notes. It formats the extracted commit history according to Keep a Changelog standards, ensuring consistent documentation of code changes for each new software version.

Can I automatically create GitHub releases from commit history without manual effort?▼

Yes, you can automatically create GitHub releases from commit history. The automation analyzes your code diffs to determine version increments, generates the changelog, commits the version update, pushes to the remote repository, and publishes the GitHub release without manual intervention.

What is the best way to determine SemVer increments from git history and code diffs?▼

The best way to determine SemVer increments from git history is by analyzing code diffs and commit messages. This automated approach evaluates the impact of changes to accurately decide whether a major, minor, or patch version bump is appropriate for the next release.

Are there limitations when using Cargo for automated version management and publishing?▼

Using Cargo for automated version management and publishing limits the workflow to projects within the Rust ecosystem. The release automation requires Cargo specifically for version management, meaning it is not directly applicable to software projects built with other package managers.