hotfix

An emergency hotfix workflow assesses incident severity, creates a traceable record, and coordinates approvals with rollback planning. You start by confirming severity to bypass normal sprint processes, then branch from a chosen base ref for minimal-change implementation.

You need an urgent git branching hotfix when a production incident requires fast remediation. The workflow classifies issues as S1/S2 or S3-and-below, confirming whether to bypass normal sprint processes for critical game-breaking bugs.

Incident response determines required QA scope—smoke check, targeted team-qa, or full QA—based on code touchpoints. Deployment verification involves merging to release and development branches, then verifying the fix in the deployed build before closing the incident.

Yes, the incident response workflow coordinates parallel approvals from lead-programmer, qa-tester, and producer. This ensures critical issues get fixed fast with rollback planning and post-deploy verification without destabilizing the game.

The best way is creating an audit-tracked hotfix record that includes problem, root cause, fix, testing, approvals, and rollback plan. This structured documentation is generated during severity triage and maintained throughout the emergency fix workflow.

Yes, the hotfix workflow requires explicit user invocation and severity confirmation via AskUserQuestion. Git branch creation is guarded by user approval, and write access to hotfix record paths is required to maintain audit-tracked documentation.