release-manager

Automate version bumps, changelog generation, and Git tag releases.

28|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/girijashankarj/cursor-handbook --skill release-manager-girijashankarj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-manager
Source: https://github.com/girijashankarj/cursor-handbook/tree/main/.cursor/skills/devops/release-manager
Command: npx skills add https://github.com/girijashankarj/cursor-handbook --skill release-manager-girijashankarj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and automate the full release lifecycle, including version bumps, changelog generation, tag creation, and publishing release notes to ensure consistent, auditable deployments.

Core Features & Use Cases

  • Automated Version Bump: Determine and apply the correct semantic version based on commit history.
  • Changelog Generation: Create and prepend release notes from commits and PRs.
  • Tagging & Release: Create Git tags and publish release notes to your repository.
  • Guardrails: Enforce prerequisites (clean working tree, CI checks, branch rules) before proceeding with any release steps.
  • Use Case: When preparing a release on main or release/* branches, run the workflow to produce a consistent release artifact.

Quick Start

Please initiate the release workflow on your main branch once all checks pass and there are no uncommitted changes.

Frequently Asked Questions about release-manager

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

FAQPage Schema
How do I automate semantic versioning and release notes generation from git commits?

Automate semantic versioning and release notes by analyzing commit history to determine the correct version bump, generating a changelog from commits and PRs, and publishing those notes to Git tags and GitHub releases.

How do I create git tags and publish GitHub releases with an automated workflow?

Create git tags and publish GitHub releases by running an automated workflow that applies a version bump, enforces a clean working tree, requires user confirmation before major steps, and pushes the final tag with generated release notes.

What's the best way to enforce a clean working tree before creating a release tag?

Enforce a clean working tree before creating a release tag by using guardrails that check for uncommitted changes, CI checks, and branch rules, halting the release workflow and requiring user confirmation if prerequisites are not met.

Can I apply a version bump across multiple package manifests and config files?

Apply a version bump across multiple package manifests and config files by running the release workflow on main or release branches, which automatically handles and updates version references throughout the repository.

Does semantic version bumping work with release branches or only main?

Semantic version bumping works with both main and release/* branches, allowing you to initiate the release workflow and produce consistent release artifacts once all CI checks pass and there are no uncommitted changes.