release

Prepare version bumps, update changelogs, and push annotated git tags.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/pzheng460/claude-workflow-plugin --skill release-pzheng460
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/pzheng460/claude-workflow-plugin/tree/main/skills/release
Command: npx skills add https://github.com/pzheng460/claude-workflow-plugin --skill release-pzheng460

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures releases are prepared correctly by guiding version bump selection, enforcing clean test and lint status, updating manifests and changelogs, and creating and pushing git tags to avoid broken or inconsistent releases.

Core Features & Use Cases

  • Version bump guidance: Compare commits and tags to recommend patch, minor, or major semver changes.
  • Pre-release verification: Require passing test and lint commands and a clean working tree before tagging.
  • Release preparation: Update version files, amend changelogs, create annotated tags, and push changes and tags to the remote; verify CI and package publication when applicable.

Quick Start

Use the release skill to choose the semver bump, run tests and linters, update version files and changelog, tag the new version, and push the tag to origin.

Frequently Asked Questions about release

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

FAQPage Schema
How do I prepare a semantic versioning release and push a git tag?

To prepare a semantic versioning release, you bump the version in manifest files, update the changelog, create an annotated git tag, and push the tag to the remote repository to trigger CI pipelines.

What's the best way to determine if my next release should be a patch, minor, or major semver bump?

To determine the correct semver bump, compare recent commits against the previous git tags to recommend whether a patch, minor, or major version increment is appropriate for the new release.

Do I need to pass tests and linters before creating an annotated git tag for a release?

Yes, creating an annotated git tag requires a clean working tree and passing test and lint commands beforehand to ensure reliable, consistent software releases without breaking the CI pipeline.

How does changelog generation work during the version bump process?

Changelog generation during a version bump involves amending the changelog file with new release entries alongside updating manifest files, ensuring documentation accurately reflects the semantic versioning changes before tagging.

Can I automate git tagging and changelog updates for my CI pipeline releases?

Automating git tagging and changelog updates streamlines CI pipeline releases by enforcing pre-release verification, updating version files, creating annotated tags, and pushing changes to the remote repository automatically.

Why should I use annotated git tags instead of lightweight tags for semantic versioning releases?

Annotated git tags store metadata like the tagger and message, providing a reliable audit trail for semantic versioning releases that lightweight tags lack, ensuring consistent release tracking across the repository.