What problem does it solve? Game code has failure modes that generic code review misses: frame-rate-dependent physics, per-frame heap allocations causing GC stutter, invalid state machine combinations, and leaked resources on scene transitions. This Skill applies game-specific checks alongside standard quality review so these issues are caught before they ship. ## Core Features & Use Cases - Eleven game-specific audits: delta time usage, hot path allocations, state management, frame-rate independence, resource cleanup, dependency direction, data-driven values, input handling, concurrency safety, AI-generated code anti-patterns, and magic numbers. - Structured severity-rated report: findings are classified Critical/Major/Minor with file and line references, plus an architecture map, positive highlights, and prioritized recommended actions. - Engine-aware review: checks are applied against the conventions of the project's engine (Godot, Unity, Unreal), with optional MCP integration for GitHub PR diffs and live engine verification. - Use Case: Before merging a combat system feature branch, run the review to catch a per-frame allocation in the particle update loop and a boolean-soup state machine that lets a character attack while dead. ## Quick Start Ask the AI to review your game code with this skill, for example: review the player controller and combat system in my Godot project for frame-rate and state machine issues.
