skills.rest
hiivmind
hiivmindOFFICIAL
Explore all skills by this author →
GitHub

prepare-release

Automate release branches, version bumps, changelogs, and PR creation to main.

Updated Jan 27, 2026
Search Tags:#automation#git#branching#release#PR#CHANGELOG#version-bump
One-click install
npx skills add https://github.com/hiivmind/hiivmind-blueprint-lib --skill prepare-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-release
Source: https://github.com/hiivmind/hiivmind-blueprint-lib/tree/main/skills/prepare-release
Command: npx skills add https://github.com/hiivmind/hiivmind-blueprint-lib --skill prepare-release

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Skill automates the end-to-end release process: creating release branches, bumping version files, drafting changelogs, committing changes, and opening a pull request to main. It helps teams standardize releases, avoid manual errors, and accelerate shipping.

## Core Features & Use Cases

  • Release branch management: creates release/vX.Y.Z branches from the current HEAD and pushes to origin.
  • Version and changelog automation: updates version fields in package files and creates a Keep a Changelog-compliant entry.
  • PR orchestration: opens a PR targeting main with a concise release summary.
  • Preconditions and safety checks: verifies a clean working tree and up-to-date main before proceeding.

### Quick Start Say "/prepare-release 4.2.0" to prepare a production release, or "/prepare-release" to auto-detect the version from changes. The skill will analyze changes, determine the appropriate version bump, create the release branch, update files, draft the changelog, push changes, and open a PR to main.

Frequently Asked Questions about prepare-release

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

FAQPage Schema
How do I automate release branch creation and version bumping?▼

You can automate release branch creation and version bumping by orchestrating branch creation from HEAD, updating version fields in package files, and pushing changes directly to origin.

Can I auto-detect the appropriate version bump from changes?▼

Yes, you can auto-detect the appropriate version bump from changes if no explicit version is provided; the system analyzes version files and changelogs to determine the correct bump.

How do I generate Keep a Changelog-compliant entries during a release?▼

Generate Keep a Changelog-compliant entries by drafting changelog updates automatically during the release process, ensuring standardized release notes are committed alongside version bumps.

What preconditions are checked before preparing a production release?▼

Preconditions checked before preparing a production release include verifying a clean working tree and ensuring your main branch is up-to-date before proceeding with branch creation.

Does the release automation open a PR to main automatically?▼

Yes, release automation opens a PR to main automatically by orchestrating the push of committed version bumps and changelog drafts with a concise release summary.

What's the best way to standardize production releases across repositories?▼

The best way to standardize production releases across repositories is automating the end-to-end process: branch creation, version bumping, changelog updates, and PR orchestration to avoid manual errors.

Related Skills

Explore More Software Engineering Skills→
webdevcodywebdevcody
22

commit-push-and-release

Commit and push working-tree changes on main, then cut and push a minor version release tag.

Community
Intermediate
DevelonautDevelonaut
3

merge-pr

Verify CI checks, detect conflicts, and squash-merge approved pull requests.

Community
Advanced
lanegridlanegrid
59

git-workflow

Enforce branching strategies, Conventional Commits, and PR workflows in Git.

Official
Intermediate
robotijnrobotijn
3

changelog-generator

Generate Keep a Changelog 1.1 compliant changelogs from Conventional Commits.

Community
Advanced