release

Automate software releases with versioning, Git tagging, and remote pushing.

62|13|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/driangle/taskmd --skill release-driangle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/driangle/taskmd/tree/main/.agents/skills/release
Command: npx skills add https://github.com/driangle/taskmd --skill release-driangle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of releasing new software versions, ensuring consistency and reducing manual effort.

Core Features & Use Cases

  • Automated Version Bumping: Increments version numbers according to semantic versioning.
  • Tagging and Pushing: Creates Git tags and pushes them to the remote repository.
  • Release Notes Generation: Compiles changelog information from commit history.
  • Use Case: When you've completed a set of features and bug fixes, use this Skill to prepare and publish a new stable release of your project.

Quick Start

Use the release skill to create a new version 1.2.3 release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate git tagging and versioning for a new release?

You can automate git tagging and versioning by using a release script that performs pre-flight checks, validates semver format, creates Git tags, and pushes them to the remote repository. This ensures consistent semantic versioning without manual effort.

How do I generate release notes from commit history automatically?

Generating release notes from commit history is handled automatically during the release process. The system compiles changelog information from your previous commits to document changes, bug fixes, and new features for the new version.

What are the prerequisites for running an automated deployment release script?

Before running an automated deployment release script, your repository must be completely clean. The pre-flight checks ensure your working directory has no uncommitted changes and the target version number strictly follows valid semver format before proceeding.

Can I push semantic version tags to a remote repository without manual commands?

Yes, you can push semantic version tags to a remote repository automatically. The release lifecycle management process validates the semver format, creates the Git tag locally, and pushes it directly to your configured remote repository.

Why does my version bump fail during the release process?

Your version bump fails during the release process if the repository is not clean or the target version violates semver format. The pre-flight checks strictly validate the repository state and version string before executing any release lifecycle scripts.