start-hotfix

Create git-flow-next hotfix branches with version bumps and pushes.

577|48|Updated Aug 4, 2025
One-click install
npx skills add https://github.com/FradSer/dotclaude --skill start-hotfix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-hotfix
Source: https://github.com/FradSer/dotclaude/tree/main/gitflow/skills/start-hotfix
Command: npx skills add https://github.com/FradSer/dotclaude --skill start-hotfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the initiation of hotfix branches in Git Flow, reducing manual steps and ensuring consistent branch naming and version updates.

Core Features & Use Cases

  • Hotfix initiation: Create a new hotfix branch using the git-flow-next CLI to isolate urgent fixes.
  • Version bump automation: Update version references across project files (e.g., package.json, Cargo.toml) as part of the hotfix process.
  • Standardized commits & push: Generate a conventional commit message for the version bump and push the new branch to origin.
  • Use Case: When a critical bug lands, start a hotfix branch, apply changes, commit with a standard message, and push for immediate collaboration.

Quick Start

Start a hotfix for a given version by running the CLI, for example: git flow hotfix start 1.2.3

Frequently Asked Questions about start-hotfix

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

FAQPage Schema
How do I start a hotfix branch and automatically bump the version in my project files?

To start a hotfix branch and bump versions, this Skill uses the git-flow-next CLI to create the branch and update version references across files like package.json. It then generates a conventional commit for the version bump and pushes the branch to origin.

What is the best way to automate git-flow hotfix initiation with consistent naming?

Automating git-flow hotfix initiation ensures consistent branch naming and version updates by using the git-flow-next CLI. This Skill orchestrates branch creation, version bumps, conventional commits, and pushes to reduce manual steps.

Can I update versions in package.json or Cargo.toml when creating a git hotfix?

Yes, you can update versions in package.json or Cargo.toml when creating a git hotfix. The Skill automates version bump updates across common project files as part of the hotfix branch creation process.

Do I need the git-flow-next CLI to automate hotfix branch creation and pushes?

Yes, you need the git-flow-next CLI installed to automate hotfix branch creation. This Skill requires the CLI and accessible Git repositories to perform branch creation, version bumps, and push orchestration.

Does starting a hotfix branch automatically generate a commit and push to origin?

Starting a hotfix branch does automatically generate a commit and push to origin. The Skill creates a standardized conventional commit message for the version bump and orchestrates pushing the new branch for immediate collaboration.

When should I use an automated hotfix workflow instead of manual git branching?

You should use an automated hotfix workflow when a critical bug lands and you need to isolate urgent fixes quickly. It reduces manual steps, ensures consistent branch naming, and standardizes version updates for immediate collaboration.