Menú
Use when patching a shipped or live-risky game and changes must stay narrow and rollback-aware.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when auditing structure, boundaries, coupling, or state-management risks in an existing game project.
Use when auditing UI sounds, reward/failure cues, danger cues, or audio feedback layering in a game.
Use when converting game audit findings into a structured multi-axis scorecard.
Use when choosing a backend profile for a game based on capabilities, project state, and quality target.
Use when reviewing a built or in-progress game against the locked brief before claiming completion.
Use when deciding development mode, quality target, task granularity, or refactor policy for game work.
| name | gsp-live-patch |
| description | Use when patching a shipped or live-risky game and changes must stay narrow and rollback-aware. |
Make a safe, reversible, production-minded change in a shipped or operationally risky project.
Follow the gsp-orchestrator output strategy:
docs/game-studio/release-safety.md, docs/game-studio/quality-report.md.Use:
./shared/templates/release-safety.md./shared/checklists/live-patch-checklist.mdThis skill exists so live work is not treated like greenfield YOLO work.