release

Guide Git Flow release and hotfix workflows with synchronized package.json versions.

Updated Aug 19, 2025
One-click install
npx skills add https://github.com/wannysim/mumak-www --skill release-wannysim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/wannysim/mumak-www/tree/main/.cursor/skills/release
Command: npx skills add https://github.com/wannysim/mumak-www --skill release-wannysim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git-flow-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a clear, step-by-step guide for managing software releases and hotfixes using Git Flow and automated version synchronization, ensuring consistency and reducing errors.

Core Features & Use Cases

  • Release Workflow: Guides through creating release branches, updating versions, committing changes, and finalizing releases.
  • Hotfix Workflow: Details the process for urgent production bug fixes, including branch creation, bug resolution, version updates, and merging.
  • Version Synchronization: Utilizes a script to ensure all package.json files within the monorepo are updated to the correct version.
  • Use Case: A development team needs to release a new feature set. This Skill will guide them through the entire Git Flow process, from starting a release branch to pushing the final tagged commit.

Quick Start

Follow the release workflow guide to start a release branch for version 1.2.0.

Frequently Asked Questions about release

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

FAQPage Schema
How do I manage Git Flow releases in a monorepo with multiple package.json files?

To manage Git Flow releases in a monorepo, this workflow guides you through creating release branches and uses a dedicated script to synchronize Semantic Versioning updates across all package.json files before committing and tagging.

What is the best way to handle an urgent production hotfix using Git Flow?

Handling an urgent production hotfix with Git Flow involves creating a dedicated hotfix branch, resolving the bug, updating the version, and merging the final tagged commit back into the main branch.

Do I need the git-flow-cli to manage release and hotfix branches?

Yes, you need the git-flow-cli dependency installed to guide the structured creation of release and hotfix branches and to execute the final merges with tag generation.

How does version synchronization work across multiple package.json files during a release?

Version synchronization works by using a dedicated script that ensures all package.json files within the monorepo are updated to the correct Semantic Versioning target during the release or hotfix process.

Can I use this workflow to apply Semantic Versioning updates across a monorepo?

Yes, you can apply Semantic Versioning updates across a monorepo by following the structured release workflow guide, which automates version synchronization across your project's package.json files.

What are the limitations of using Git Flow for monorepo release management?

The Git Flow release management workflow requires strict adherence to its structured branch creation and merging process, relying on the git-flow-cli and a specific version synchronization script for package.json files.