release

Automate release management with version bumping, branch merging, tagging, and pushing.

Updated Oct 24, 2025
One-click install
npx skills add https://github.com/5hdaniel/Mad --skill release-5hdaniel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/5hdaniel/Mad/tree/main/.claude/skills/release
Command: npx skills add https://github.com/5hdaniel/Mad --skill release-5hdaniel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release management for software projects is error-prone and repetitive, requiring careful coordination of version bumps, branch merges, tag creation, and pushes. This Skill provides a structured workflow to ensure releases are consistent, auditable, and reversible.

Core Features & Use Cases

  • Version bump coordination and conventional-commit friendly messages.
  • Safe merge of develop into main with no-fast-forward merges and automatic tagging.
  • Clear rollback guidance and changelog visibility for release auditing.

Quick Start

Execute /release to cut a new release from develop to main after confirming all PRs are merged and CI checks pass.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate merging develop into main with version bumping and tagging?

Automating git release workflows ensures safe, auditable steps by coordinating version bumps, merging develop into main with no-fast-forward, creating tags, and pushing only after all PRs merge and CI checks pass.

What do I need to set up before automating a multi-branch release workflow?

Before automating a multi-branch release workflow, you need a Git repository with develop and main branches, a package.json for version bumping, and the GitHub CLI (gh) to verify PR merges and CI checks.

Can I use this release automation if my CI checks are still running?

You should not use this release automation while CI checks are running. The workflow requires all PRs to be merged and all CI checks to pass before it executes the version bump, merge, and tagging process.

How does this approach handle rollback and changelog visibility for auditing?

This approach handles rollback and changelog visibility by generating changelogs during the release process and providing clear rollback guidance, ensuring every version bump and merge step remains auditable and reversible.

What is the best way to coordinate conventional-commit friendly version bumps?

The best way to coordinate conventional-commit friendly version bumps is using an automated workflow that updates package.json versions, merges develop into main, and tags the release, ensuring consistent and structured versioning.