hotfix

Name: hotfix
Availability: InStock
Author: lekay

Create a hotfix branch, track approvals, and backport fixes.

Updated May 24, 2026

Search Tags:#git #bug fixing #branch management #code audit #hotfix

Ready to run

npx skills add https://github.com/LeKay/ai-game --skill hotfix-lekay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/LeKay/ai-game/tree/main/.claude/skills/hotfix
Command: npx skills add https://github.com/LeKay/ai-game --skill hotfix-lekay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, Task, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of implementing emergency fixes to bypass normal sprint processes while maintaining a full audit trail.

Core Features & Use Cases

Emergency Fix Workflow: Bypasses normal sprint processes with a full audit trail.
Hotfix Branch Creation: Creates a hotfix branch for the fix.
Approvals and Backporting: Tracks approvals and ensures the fix is backported correctly.
Use Case: When a critical bug is discovered that requires immediate attention, this Skill can be used to create a hotfix branch, track approvals, and implement the fix.

Quick Start

Run the /hotfix command followed by the bug ID or description.

Frequently Asked Questions about hotfix

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

FAQPage Schema

How do I create a git hotfix branch for a critical bug without interrupting the normal sprint process?▼

To create a git hotfix branch that bypasses normal sprint processes, this Skill initiates an emergency fix workflow that directly branches off the main codebase. It isolates the critical bug fix while maintaining a full audit trail of the changes made.

What is the best way to track approvals and ensure a critical bug fix is backported correctly?▼

Tracking approvals and ensuring correct backporting of a critical bug fix is handled by the integrated emergency workflow using the Task tool. It records authorization steps and automates the backporting sequence to guarantee the fix is applied to all necessary release branches.

Do I need git installed to manage emergency code fixes and audit trails?▼

Yes, you need git installed to manage emergency code fixes and audit trails, as this Skill relies on git for branch management. It uses git commands to create the hotfix branch and track the code audit history required for compliance.

Can I use this emergency fix workflow for non-critical bugs that do not require immediate attention?▼

This emergency fix workflow is intended specifically for critical bug fixes that need to be addressed immediately, bypassing standard sprint processes. Using it for non-critical bugs is discouraged due to the strict approval tracking and immediate backporting mechanisms involved.

How does the hotfix workflow handle code audits for immediate bug fixes?▼

The hotfix workflow handles code audits for immediate bug fixes by enforcing an emergency fix workflow that tracks approvals and maintains a full audit trail. This ensures every bypass of the normal sprint process is documented and reviewed for compliance.

How do I start an emergency fix using a bug ID or description?▼

You start an emergency fix by running the hotfix command followed by the specific bug ID or a brief description. This triggers the workflow to create the hotfix branch, log the code audit, and prepare the environment for the critical bug fix.