release

Automate version bumping, changelog updates, Git tagging, and code pushing for software releases.

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

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 cutting a software release, ensuring consistency and adherence to best practices.

Core Features & Use Cases

  • Automated Versioning: Determines the next semantic version (MAJOR.MINOR.PATCH) based on project history.
  • Changelog Generation: Integrates with a /changelog command or manual updates to keep release notes current.
  • Git Workflow: Handles version bumping, committing, tagging, and pushing to remote repositories.
  • Use Case: A developer needs to release a new version of the software. They can invoke this skill, which will automatically check tests, determine the correct version number, update relevant files, commit the changes, tag the release, and push everything to the main branch and tags.

Quick Start

Use the release skill to cut a new patch release.

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 Git tagging for a new software release?

Automating semantic versioning and Git tagging is handled by this Skill, which determines the next version bump, updates files, creates Git tags, and pushes changes to remote repositories. It enforces semantic rules and pre-release validation checks.

What is the best way to generate changelogs and cut a release automatically?

Generating changelogs and cutting a release is streamlined by this Skill through integration with a `/changelog` command or manual updates, ensuring release notes are current before version bumping and deployment.

How does semantic version bumping work when preparing a deployment?

Semantic version bumping for deployment works by analyzing project history to determine the correct MAJOR.MINOR.PATCH increment, automatically updating relevant files, and committing the changes before tagging.

Can I enforce pre-release validation checks before pushing Git tags?

Yes, pre-release validation checks are enforced automatically before pushing Git tags, ensuring tests pass and the codebase is stable for an auditable release pipeline.

Does this release automation tool work without external dependencies?

Yes, this release automation tool works without external dependencies, managing version bumping, changelog updates, Git tagging, and code pushing entirely through its internal scripts and references.

Why should I use an automated release pipeline instead of manual version bumping?

An automated release pipeline prevents human error in manual version bumping by enforcing semantic rules, running validation checks, and standardizing Git commits and tags for a consistent, auditable deployment process.