hotfix

Create audit-tracked hotfix branches with approvals and QA gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of deploying urgent fixes without skipping necessary review, testing, audit documentation, or correct backporting.

Core Features & Use Cases

  • Severity-based triage: Classifies issues as S1/S2 and stops if a hotfix is not warranted (S3 or lower), directing teams to normal bug-fix workflow.
  • Audit-tracked hotfix record: Creates a structured hotfix log with problem, root cause, fix, testing, approvals, and rollback plan.
  • Branching, approvals, and QA gates: Creates a dedicated hotfix branch, collects required sign-offs (lead-programmer, qa-tester, producer), runs the appropriate QA gate (smoke check vs team-qa vs full QA), then updates status and coordinates deployment merges.

Quick Start

Request the workflow by explicitly asking: /hotfix with a bug-id or a brief description of what is broken and how badly it impacts players.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I manage an emergency hotfix for a severe production incident without skipping code review?

Managing an emergency hotfix requires severity-based triage, a dedicated git branching strategy, mandatory approvals, and QA validation gates to deploy fast while maintaining traceability and rollback safety.

When should I use a dedicated hotfix branch instead of a normal bug-fix workflow?

Use a dedicated hotfix branch for S1 or S2 production incidents and severe regressions where a minimal-change fix must be deployed quickly. S3 or lower issues should follow a normal bug-fix workflow instead.

What approvals and QA gates are required to deploy a critical production hotfix?

Deploying a critical production hotfix requires sign-offs from lead-programmer, qa-tester, and producer, plus passing the appropriate QA gate ranging from a smoke check to full QA validation before deployment merges.

How do I document a rollback plan and audit trail during incident response?

Documenting a rollback plan and audit trail during incident response involves creating a structured hotfix record logging the problem, root cause, fix, testing, approvals, and rollback documentation for post-deploy verification.

Does this hotfix workflow handle regression coverage and backporting after deployment?

Yes, the hotfix workflow enforces regression coverage and correct backporting by running severity triage, QA re-entry gating, and post-deploy verification steps to ensure the minimal-change fix is safely integrated.