release

Bump semver versions and generate changelog-backed annotated git tags.

22|3|Updated Jul 28, 2024
One-click install
npx skills add https://github.com/webdevcody/go-mailing-list --skill release-webdevcody
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/webdevcody/go-mailing-list/tree/main/.claude/skills/release
Command: npx skills add https://github.com/webdevcody/go-mailing-list --skill release-webdevcody

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Releasing a project safely and consistently by bumping the right version(s), generating accurate release notes, and avoiding common mistakes like dirty-tree releases or overwriting tags.

Core Features & Use Cases

  • Phased, guardrailed release workflow: checks for a clean working tree, correct branch, and existing tags before making any changes.
  • Correct version bumping across common manifest types: supports package.json, pyproject.toml, Cargo.toml, plain VERSION files, and Claude Code plugin marketplaces.
  • Diff-driven marketplace releases: when .claude-plugin/marketplace.json is present, bumps the marketplace plus only the per-plugin versions whose code changed since the last tag, following a dedicated reference rule file.
  • Commit, annotated tag, and release notes generation: creates an annotated git tag with release notes derived from commits since the last tag (or all commits if no prior tag exists), with conventional-commit grouping when detectable.

Quick Start

Ask the skill to cut a release with the desired bump type, for example: "Cut a release patch for this repo."

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate semver version bumping and generate release notes from git commits?

To automate semver version bumping and release note generation, this skill derives annotated git tags from commit history since the last tag, grouping conventional commits automatically. It bumps manifest versions across Node, Python, Rust, or plain VERSION files.

How do I safely cut a release without overwriting existing git tags or committing a dirty tree?

To safely cut a release without overwriting git tags or committing a dirty tree, this skill enforces a preflight validation phase that halts the process entirely if the working tree is dirty, the branch is incorrect, or the target tag already exists.

Does this release automation tool support diff-driven version bumping for Claude Code plugin marketplaces?

Yes, this release automation tool supports diff-driven version bumping for Claude Code plugin marketplaces. When .claude-plugin/marketplace.json is detected, it bumps the marketplace and only updates per-plugin versions whose code changed since the last tag.

What is the best way to cut a patch release across multiple manifest types like Cargo.toml and pyproject.toml?

The best way to cut a patch release across manifests like Cargo.toml and pyproject.toml is to trigger a phased workflow that detects supported manifest files, syncs lockfiles, applies the version bump, and prepares a commit-ready package with annotated tags.

Why does my release tagging workflow fail when my repository has no prior git tags?

Release tagging workflows do not fail when no prior git tags exist; instead, this skill generates release notes derived from all available commits in the repository history, ensuring a complete changelog-backed annotated tag is still created.

Can I use this skill to generate changelog-backed annotated git tags without a CI-CD pipeline?

Yes, you can use this skill to generate changelog-backed annotated git tags without a CI-CD pipeline. It operates directly within your local git workflow, applying semver bumps and preparing a commit-ready release package independently.