# Hotfix > Flujo de arreglo urgente que se salta el proceso normal de sprint pero deja rastro de auditoría completo: crea rama hotfix, registra aprobaciones y asegura el backport correcto. Fuente: https://skillsagentes.com/skills/donchitos/claude-code-game-studios/hotfix Markdown: https://skillsagentes.com/skills/donchitos/claude-code-game-studios/hotfix.md Repositorio: https://github.com/Donchitos/Claude-Code-Game-Studios Autor: Donchitos Licencia: MIT Actualizado: hace 3 meses Coste de contexto: 43 tok instalada, 1.6k tok al activarse, 1.6k tok con todos los archivos del bundle Bundle: 1 archivo, 6 KB Permisos que pide: read, glob, grep, write, edit, bash, task, askuserquestion ## Instalación Un skill son archivos markdown: los mismos archivos valen para cualquier agente y lo único que cambia es el directorio de destino, es decir la bandera `--agent`. Añade `-g` para instalarlo en todos los proyectos de la máquina. ```bash # Claude Code npx -y skills add Donchitos/Claude-Code-Game-Studios --skill hotfix --agent claude-code # Cursor npx -y skills add Donchitos/Claude-Code-Game-Studios --skill hotfix --agent cursor # Codex npx -y skills add Donchitos/Claude-Code-Game-Studios --skill hotfix --agent codex # Gemini CLI npx -y skills add Donchitos/Claude-Code-Game-Studios --skill hotfix --agent gemini # Windsurf npx -y skills add Donchitos/Claude-Code-Game-Studios --skill hotfix --agent windsurf # Cline npx -y skills add Donchitos/Claude-Code-Game-Studios --skill hotfix --agent cline ``` ## Qué hace - Assesses bug severity (S1/S2/S3) and confirms with the user before proceeding - Creates a hotfix record file with problem, root cause, fix, testing and approvals sections - Creates a hotfix git branch after confirming base ref - Collects parallel sign-off from lead-programmer, qa-tester and producer via Task tool - Runs a QA re-entry gate (smoke check or team-qa) before allowing deployment ## Cuándo usarla - User explicitly invokes /hotfix for a critical or major production bug - A game-breaking, data-loss or security issue needs an emergency fix with audit trail ## Cuándo no - Issue is S3 or lower — redirect to the normal bug fix workflow ## Qué la activa - "/hotfix el juego crashea al guardar partida" - "/hotfix vulnerabilidad de seguridad en el login" - "/hotfix BUG-142" ## Antes de instalar - Funciona mejor dentro de un repositorio git y asume subagentes como lead-programmer, qa-tester, producer y qa-lead disponibles vía Task. - runs shell commands - writes to your files ## Archivos - SKILL.md — 6 KB ## SKILL.md Reproducido tal cual desde Donchitos/Claude-Code-Game-Studios bajo MIT. Esta sección es el documento original y está en inglés. > **Explicit invocation only**: This skill should only run when the user explicitly requests it with `/hotfix`. Do not auto-invoke based on context matching. ## Phase 1: Assess Severity Read the bug description or ID. Assess severity using these criteria: - **S1 (Critical)**: Game unplayable, data loss, security vulnerability - **S2 (Major)**: Significant feature broken, workaround exists - **S3 or lower**: Minor issue — normal bug fix workflow applies Confirm with `AskUserQuestion`: - Prompt: "I've assessed this as **[assessed severity]** — [brief rationale]. Confirm severity to proceed:" - Options: - `[A] S1 (Critical) — game unplayable, data loss, or security issue` - `[B] S2 (Major) — significant feature broken, workaround exists` - `[C] S3 or lower — redirect to normal bug fix workflow` If [C]: stop. Verdict: **REDIRECTED** — use the normal bug fix workflow for S3 and below. --- ## Phase 2: Create Hotfix Record Draft the hotfix record: ```markdown ## Hotfix: [Short Description] Date: [Date] Severity: [S1/S2] Reporter: [Who found it] Status: IN PROGRESS ### Problem [Clear description of what is broken and the player impact] ### Root Cause [To be filled during investigation] ### Fix [To be filled during implementation] ### Testing [What was tested and how] ### Approvals - [ ] Fix reviewed by lead-programmer - [ ] Regression test passed (qa-tester) - [ ] Release approved (producer) ### Rollback Plan [How to revert if the fix causes new issues] ``` Ask: "May I write this to `production/hotfixes/hotfix-[date]-[short-name].md`?" If yes, write the file, creating the directory if needed. --- ## Phase 3: Create Hotfix Branch Check whether this is a git repository: `Bash: git rev-parse --is-inside-work-tree 2>/dev/null` If this command fails or returns empty: note "Not a git repository — create the branch manually." and skip branch creation. If the check passes, use `AskUserQuestion` before creating the branch: - Prompt: "Ready to create hotfix branch 'hotfix/[short-name]' from [base-ref]?" - Options: - `[A] Yes — create branch` - `[B] Use a different base ref — I'll specify it` - `[C] Skip — I'll create the branch myself` Only run `git checkout -b hotfix/[short-name] [base-ref]` if user selects [A]. If [B]: ask the user for the base ref, then run the command with that ref. If [C]: skip branch creation and proceed to Phase 4. --- ## Phase 4: Investigate and Implement Focus on the minimal change that resolves the issue. Do NOT refactor, clean up, or add features alongside the hotfix. Validate the fix by running targeted tests for the affected system. Check for regressions in adjacent systems. Update the hotfix record with root cause, fix details, and test results. --- ## Phase 5: Collect Approvals Use the Task tool to request sign-off in parallel: - `subagent_type: lead-programmer` — Review the fix for correctness and side effects - `subagent_type: qa-tester` — Run targeted regression tests on the affected system - `subagent_type: producer` — Approve deployment timing and communication plan All three must return APPROVE before proceeding. If any returns CONCERNS or REJECT, do not deploy — surface the issue and resolve it first. --- ## Phase 5b: QA Re-Entry Gate After approvals, determine the QA scope required before deploying the hotfix. Spawn `qa-lead` via Task with: - The hotfix description and affected system - The regression test results from Phase 5 - A list of all systems that touch the changed files (use Grep to find callers) Ask qa-lead: **Is a full smoke check sufficient, or does this fix require a targeted team-qa pass?** Apply the verdict: - **Smoke check sufficient** — run `/smoke-check` against the hotfix build. If PASS, proceed to Phase 6. - **Targeted QA pass required** — run `/team-qa [affected-system]` scoped to the changed system only. If QA returns APPROVED or APPROVED WITH CONDITIONS, proceed to Phase 6. - **Full QA required** — S1 fixes that touch core systems may require a full `/team-qa sprint`. This delays deployment but prevents a bad patch. Do not skip this gate. A hotfix that breaks something else is worse than the original bug. --- ## Phase 6: Update Bug Status and Deploy Update the original bug file if one exists: ```markdown ## Fix Record **Fixed in**: hotfix/[branch-name] — [commit hash or description] **Fixed date**: [date] **Status**: Fixed — Pending Verification ``` Set `**Status**: Fixed — Pending Verification` in the bug file header. Output a deployment summary: ``` ## Hotfix Ready to Deploy: [short-name] **Severity**: [S1/S2] **Root cause**: [one line] **Fix**: [one line] **QA gate**: [Smoke check PASS / Team-QA APPROVED] **Approvals**: lead-programmer ✓ / qa-tester ✓ / producer ✓ **Rollback plan**: [from Phase 2 record] Merge to: release branch AND development branch Next: /bug-report verify [BUG-ID] after deploy to confirm resolution ``` ### Rules - Hotfixes must be the MINIMUM change to fix the issue — no cleanup, no refactoring - Every hotfix must have a rollback plan documented before deployment - Hotfix branches merge to BOTH the release branch AND the development branch - All hotfixes require a post-incident review within 48 hours - If the fix is complex enough to need more than 4 hours, escalate to `technical-director` --- ## Phase 7: Post-Deploy Verification After deploying, run `/bug-report verify [BUG-ID]` to confirm the fix resolved the issue in the deployed build. If VERIFIED FIXED: run `/bug-report close [BUG-ID]` to formally close it. If STILL PRESENT: the hotfix failed — immediately re-open, assess rollback, and escalate. Schedule a post-incident review within 48 hours using `/retrospective hotfix`. Use `AskUserQuestion`: - Prompt: "Hotfix complete. What's the next step?" - Options: - `[A] Run /smoke-check to verify the fix` - `[B] Run /patch-notes to document this hotfix` - `[C] Stop here` ## Dónde encaja - Categoría: [Herramientas para desarrolladores](https://skillsagentes.com/categorias/herramientas-desarrollo.md) — Skills que cambian cómo tu agente escribe, revisa y despliega código. - Creador: [Donchitos](https://skillsagentes.com/creators/donchitos.md) — 73 skills en el directorio - [Todas las skills](https://skillsagentes.com/skills.md) - [Ranking de instalaciones](https://skillsagentes.com/ranking.md) ## Otras skills del mismo repositorio - [Team Qa](https://skillsagentes.com/skills/donchitos/claude-code-game-studios/team-qa.md): Orquesta al equipo de QA (qa-lead y qa-tester) para producir un paquete completo de QA: plan de pruebas, smoke check, casos de prueba, ejecución manual y reporte de sign-off. - [Consistency Check](https://skillsagentes.com/skills/donchitos/claude-code-game-studios/consistency-check.md): Compara todos los GDDs contra el registro de entidades para detectar inconsistencias entre documentos: mismo stat, ítem o fórmula con valores distintos, usando un enfoque grep-first. - [Create Architecture](https://skillsagentes.com/skills/donchitos/claude-code-game-studios/create-architecture.md): Redacción guiada, sección por sección, del documento de arquitectura maestro del juego, consciente de la versión del motor y de sus posibles brechas de conocimiento. - [Day One Patch](https://skillsagentes.com/skills/donchitos/claude-code-game-studios/day-one-patch.md): Prepara un patch day-one para el lanzamiento de un juego: define alcance, prioriza, implementa y valida con un QA gate ligero, como un mini-sprint con plan de rollback. - [Adopt](https://skillsagentes.com/skills/donchitos/claude-code-game-studios/adopt.md): Onboarding brownfield: audita el cumplimiento de formato de los artefactos existentes, clasifica los vacíos por impacto y genera un plan de migración numerado. ## Skills relacionadas - [Create Architecture](https://skillsagentes.com/skills/donchitos/claude-code-game-studios/create-architecture.md): Redacción guiada, sección por sección, del documento de arquitectura maestro del juego, consciente de la versión del motor y de sus posibles brechas de conocimiento. - [Team Qa](https://skillsagentes.com/skills/donchitos/claude-code-game-studios/team-qa.md): Orquesta al equipo de QA (qa-lead y qa-tester) para producir un paquete completo de QA: plan de pruebas, smoke check, casos de prueba, ejecución manual y reporte de sign-off. - [Consistency Check](https://skillsagentes.com/skills/donchitos/claude-code-game-studios/consistency-check.md): Compara todos los GDDs contra el registro de entidades para detectar inconsistencias entre documentos: mismo stat, ítem o fórmula con valores distintos, usando un enfoque grep-first. - [Day One Patch](https://skillsagentes.com/skills/donchitos/claude-code-game-studios/day-one-patch.md): Prepara un patch day-one para el lanzamiento de un juego: define alcance, prioriza, implementa y valida con un QA gate ligero, como un mini-sprint con plan de rollback. - [Patch Notes](https://skillsagentes.com/skills/donchitos/claude-code-game-studios/patch-notes.md): Genera notas de parche para jugadores a partir del historial de git, datos de sprint y changelogs internos, traduciendo el lenguaje técnico a una comunicación clara y atractiva. --- Skills Agentes · [Índice de páginas en markdown](https://skillsagentes.com/sitemap.md) · [Inicio](https://skillsagentes.com/index.md)