hotfix

Coordinate emergency bug fixes with approvals, QA gating, and backporting.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill hotfix-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/hotfix
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill hotfix-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of unplanned, untracked emergency bug fixes for game development projects by providing a structured, auditable workflow that bypasses slow normal sprint processes while ensuring all fixes are properly documented, approved, and backported to avoid regressions.

Core Features & Use Cases

  • Severity Triage: Automatically classifies bugs as S1 (critical, game unplayable/data loss), S2 (major feature broken), or redirects minor S3 issues to the standard bug fix workflow.
  • End-to-End Hotfix Tracking: Creates standardized hotfix records, manages git branch creation, coordinates parallel approvals from lead programmers, QA testers, and producers, and enforces QA gating before deployment.
  • Post-Deploy Safety: Includes mandatory rollback plans, post-deploy verification steps, and 48-hour post-incident review scheduling to minimize risk of bad patches. Use Case: If your 90s F1-style racing game has a critical bug that crashes when players load a track, use this Skill to quickly implement a minimal fix, get all required approvals, deploy safely, and confirm the issue is resolved without disrupting ongoing sprint work.

Quick Start

Use the hotfix skill to fix the critical bug where the game crashes when loading the Monaco race track.

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 game-breaking bug without disrupting the sprint workflow?

An emergency hotfix bypasses standard sprint workflows by creating a dedicated branch, applying minimal fixes, coordinating cross-team approvals, enforcing QA gating, and backporting changes to release and development branches to prevent regressions.

What is the severity triage process for production game bug fixes?

Severity triage classifies game bugs as S1 for critical issues like data loss or unplayable states, S2 for major broken features, and redirects minor S3 issues back to the standard bug fix workflow.

How do I backport a critical game fix to both release and development branches?

Backporting a critical game fix involves applying the minimal patch to the release branch, verifying it through QA gating, and merging the changes back into the development branch to maintain codebase parity and prevent regressions.

Does the emergency hotfix workflow include post-deploy verification and rollback planning?

Yes, the emergency hotfix workflow mandates rollback plans, post-deploy verification steps, and schedules a 48-hour post-incident review to ensure production game safety and minimize bad patches.

When should I bypass the sprint workflow for a game bug fix?

You should bypass the sprint workflow when game-breaking issues, data loss vulnerabilities, or major feature breakages require immediate minimal fixes that cannot wait for standard development cycles.

How do I track approvals for an emergency game patch?

Emergency game patch approvals are tracked through parallel workflows that require sign-off from lead programmers, QA testers, and producers, ensuring full audit trails before deployment.