release-version

Automate semantic versioning and release execution for git-based projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the entire release workflow by detecting the current version, analyzing changes since the last release, and suggesting the appropriate version bump.

Core Features & Use Cases

  • Detects the current version from git tags and package.json.
  • Analyzes commits and diffs since the last release to determine patch, minor, or major increments.
  • Executes release steps including updating the version, committing, tagging, pushing, and triggering CI.

Quick Start

Trigger a release by saying 请发版本 or running the release script in your project's environment.

Frequently Asked Questions about release-version

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

FAQPage Schema
How do I automate semantic versioning and releases in a git workflow?

Automate semantic versioning by analyzing git commits since the last release to determine patch, minor, or major bumps, then updating package.json, committing, tagging, and pushing the new version automatically.

How does semantic version bump detection work from git tags?

Semantic version bump detection reads the current version from git tags and package.json, then analyzes commit messages and diffs since that tag to decide whether to increment patch, minor, or major version numbers.

Can I trigger a release version bump through CI pipelines?

Yes, you can trigger a release version bump by running the release script in your project environment or issuing a command, which updates the version and triggers the CI release process automatically.

Do I need npm-style versioning to use automated release tagging?

Automated release tagging requires npm-style versioning and a git-based workflow. It reads the current version from package.json and git tags to calculate the next semantic version increment.

What's the best way to manage patch, minor, and major version increments?

Manage version increments by analyzing commit history and diffs since the last release, allowing the automation to suggest and execute the appropriate patch, minor, or major version bump based on code changes.

Why does my automated release workflow fail to push git tags?

Automated release workflows require proper git permissions to commit, tag, and push. Ensure your CI pipeline has write access to the repository to complete the tagging and pushing steps successfully.