release

Automate version detection, changelog updates, and Git tag publishing.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/maggit/claude-workspace --skill release-maggit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/maggit/claude-workspace/tree/main/skills/release
Command: npx skills add https://github.com/maggit/claude-workspace --skill release-maggit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates release management across projects to ensure consistent versioning, changelogs, and tags.

Core Features & Use Cases

  • Automatic version detection across common manifests (package.json, pyproject.toml, Cargo.toml, version.txt) and the latest Git tag.
  • Determine bump type using conventional commits, with optional user overrides.
  • Generate structured release notes, update CHANGELOG, update manifests, and create Git tags; optionally publish a GitHub release.

Quick Start

Run the release manager to draft the next version and generate the release notes.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate semantic versioning and changelog generation from conventional commits?

Semantic versioning and changelog generation are automated by parsing conventional commits to determine the bump type, computing the next version from manifests or the latest tag, and updating the CHANGELOG with structured release notes.

Can I automatically bump versions across multiple manifests like package.json and Cargo.toml?

Yes, automatic version detection and bumping work across package.json, pyproject.toml, Cargo.toml, and version.txt. The release manager computes the bump and updates manifests to ensure consistent versioning across projects.

Does this release management approach support monorepo and multi-repo setups?

Release management supports both multi-repo and monorepo setups. It handles version detection from manifests and the latest Git tag, computing appropriate bumps, generating notes, and publishing Git tags or GitHub releases consistently.

How do I create a GitHub release and git tag with generated release notes?

Creating a GitHub release and Git tag is handled by generating structured release notes, updating the changelog and manifests, and optionally publishing via the gh CLI alongside creating the corresponding Git tag.

Can I override the automatic version bump type determined by conventional commits?

Yes, the version bump type determined by conventional commits can be overridden with user inputs. This allows manual control over the semantic versioning bump while still automating changelog updates and tag creation.