release

Automate version bumps, changelog updates, commits, tags, pushes, and installer builds.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/mcsdodo/kniha-jazd --skill release-mcsdodo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/mcsdodo/kniha-jazd/tree/main/.claude/skills/release-skill
Command: npx skills add https://github.com/mcsdodo/kniha-jazd --skill release-mcsdodo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release management is manual and error-prone; this Skill automates the end-to-end release workflow from version bump to installer build.

Core Features & Use Cases

  • Automated Version Bump: bump versions in package.json and related files across the repo.
  • Changelog Update: update CHANGELOG.md with new release notes.
  • Git Ops: commit, tag, and push changes to the VCS.
  • Build Release Installer: run the full build to generate the installer.

Quick Start

Trigger the release workflow to bump versions, update the changelog, commit and tag, push to the repository, and build the installer.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumping and changelog updates for a Tauri project?

Automated version bumping for a Tauri project updates package.json, src-tauri/Cargo.toml, src-tauri/tauri.conf.json, and CHANGELOG.md simultaneously. It enforces running tests and building the installer before committing, tagging, and pushing changes to your repository.

What is the best way to streamline release workflows from version bump to installer build?

Streamlining release workflows involves automating end-to-end tasks: bumping versions across configuration files, updating changelogs, running tests, executing builds, and handling Git operations like tagging and pushing to eliminate manual errors.

Can I use this automated release workflow if my project only has a package.json file?

This automated release workflow applies to software projects with package.json and build configurations like src-tauri. It enforces updating src-tauri/Cargo.toml and src-tauri/tauri.conf.json, so it best suits projects using the Tauri framework.

Does the release process run tests before tagging and pushing to Git?

Yes, the release process runs tests before tagging and pushing to Git. It enforces a full build to generate the installer, ensuring that code is validated and packaged successfully before changes are committed and pushed to the repository.

How do I update CHANGELOG.md automatically when preparing a new software release?

To update CHANGELOG.md automatically during a release, the workflow appends new release notes as part of the version bump cycle. It modifies the changelog alongside package.json and Tauri configurations, then commits the changes.

Why should I automate Git operations like tagging and pushing during a release?

Automating Git operations during a release prevents manual errors by ensuring tags and commits are pushed only after successful tests and builds. It creates a consistent, error-free end-to-end workflow from version bump to installer generation.