hotfix

Create a hotfix branch from a release tag, apply bug fixes, and merge back into main.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mckalexee/ruby-slippers --skill hotfix-mckalexee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/mckalexee/ruby-slippers/tree/main/.claude/skills/hotfix
Command: npx skills add https://github.com/mckalexee/ruby-slippers --skill hotfix-mckalexee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The hotfix procedure provides a fast, controlled way to patch a published release without introducing unreleased changes from the main branch.

Core Features & Use Cases

  • Create a short-lived hotfix branch from the release tag to isolate bug fixes.
  • Update CHANGELOG and RELEASE_NOTES, then tag and push the fix to the designated release.
  • Merge the hotfix back into main to preserve a clean history and prevent drift from unreleased work.

Quick Start

Create a hotfix branch from the release tag, implement the bug fix, and push the updated release notes.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I patch a released git branch without including unreleased changes from main?

To patch a released git branch safely, create a short-lived hotfix branch directly from the release tag, apply the bug fix, and then merge it back into main to prevent unreleased work from leaking.

What is the best way to update changelog and release notes for a git hotfix?

The best way to update changelog and release notes during a git hotfix is to modify them within the isolated hotfix branch before tagging and pushing the fix to the designated release.

When do I need to create a hotfix branch from a release tag?

You need to create a hotfix branch from a release tag when a published version has a critical bug and you must patch it quickly without pulling in unreleased changes from the main branch.

How does a git hotfix workflow preserve history and prevent drift?

A git hotfix workflow preserves history by applying the fix to a short-lived branch from the release tag and then merging that hotfix back into main, ensuring the codebase avoids drift from unreleased work.

Can I push a tag-based release directly from a hotfix branch?

Yes, you can push a tag-based release directly from a hotfix branch after updating the changelog and release notes, ensuring the published version receives the isolated bug fix.

Why should I avoid applying release bug fixes directly to the main branch?

Applying release bug fixes directly to main risks leaking unreleased changes into the published version, which is why creating a focused hotfix branch from the release tag provides a controlled patching process.