hotfix

Automate emergency hotfix workflows with approvals and rollback planning.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dawn840705/claude-code-game-studios --skill hotfix-dawn840705
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/dawn840705/claude-code-game-studios/tree/main/skills/hotfix
Command: npx skills add https://github.com/dawn840705/claude-code-game-studios --skill hotfix-dawn840705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves emergency software bugs by bypassing standard sprint processes while preserving a full audit trail, approvals, and backport tracking.

Core Features & Use Cases

  • Automated severity assessment, hotfix record creation, and backport readiness.
  • Optional hotfix branch creation when git is initialized, with structured approvals and rollback planning.
  • Clear deployment gates, QA coordination, and post-deploy verification.
  • Supports retrospective scheduling for post-incident review.

Quick Start

Invoke /hotfix with a bug description to generate a hotfix record and begin the remediation workflow.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I handle emergency bug fixes while maintaining a full audit trail?

This Skill automates emergency hotfix workflows by enforcing controlled approvals, generating hotfix branch scaffolding, and documenting rollout and rollback steps to preserve a full audit trail.

What is the best way to automate hotfix branch creation and approval gates?

The best way to automate hotfix branch creation is to initialize git scaffolding upon incident detection, then route the fix through structured deployment gates and required approvals before merging.

Can I use this emergency hotfix workflow without a git repository initialized?

Yes, you can use this hotfix workflow without git initialized, but it will skip automated hotfix branch scaffolding and focus solely on severity assessment, approval routing, and backport documentation.

How does rollback planning work for incident-driven bug fixes?

Rollback planning for incident-driven bug fixes works by documenting explicit rollback steps during hotfix record creation, ensuring deployment gates verify post-deploy stability before completing the workflow.

When do I need to schedule a retrospective for post-incident review?

You need to schedule a retrospective for post-incident review after completing the emergency hotfix deployment and post-deploy verification to evaluate the incident-driven fix and sprint bypass.