hotfix

Create auditable hotfix branches with sign-offs and rollback procedures.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LordKuper/agentic-game-studio --skill hotfix-lordkuper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/LordKuper/agentic-game-studio/tree/main/.claude/skills/hotfix
Command: npx skills add https://github.com/LordKuper/agentic-game-studio --skill hotfix-lordkuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Emergency production bug fixes can derail sprint plans; this skill provides a fast, auditable hotfix workflow that bypasses normal sprint processes while preserving a complete audit trail.

Core Features & Use Cases

  • Create a hotfix record, track approvals, and backport fixes across branches
  • Generate minimal, targeted changes with a clear rollback plan
  • Explicit invocation and audit-ready history ensure traceability in production incidents

Quick Start

Invoke the hotfix command with a bug-id or description to start an auditable hotfix workflow.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I manage emergency production bug fixes without derailing sprint plans?

An auditable hotfix workflow automates emergency production bug fixes to bypass normal sprint processes while preserving a complete history. It allows rapid incident resolution in live games while maintaining traceability of changes and approvals.

What is the best way to backport emergency fixes across git branches?

The best way to backport emergency fixes is using a structured hotfix workflow that creates a dedicated branch, applies minimal targeted changes, and systematically backports the fix across branches. This maintains consistency without disrupting ongoing development.

How do I track approvals and sign-offs during a critical live game incident?

You can track approvals during a live game incident by creating a hotfix record that collects sign-offs from key roles. This ensures explicit invocation and audit-ready history for traceability during production emergencies.

Does this hotfix workflow require a rollback plan for production incidents?

Yes, the hotfix workflow requires a rollback plan for production incidents. It generates minimal, targeted changes accompanied by a clear rollback procedure to ensure safe deployment and rapid recovery if needed.

How do I start an auditable hotfix workflow for a production bug?

To start an auditable hotfix workflow, invoke the hotfix command with a bug-id or description. This initiates the process of creating a hotfix record, collecting approvals, and backporting fixes across branches.

When should I use an emergency hotfix workflow instead of standard branching?

Use an emergency hotfix workflow instead of standard branching for urgent incidents in live games requiring rapid fixes. It enforces minimal-change scope and explicit approvals, making it ideal when normal sprint processes are too slow.