What problem does it solve? When AI or developers write game code quickly, it is hard to verify that changes follow project conventions before committing. This Skill turns vague quality goals into a concrete five-axis inspection checklist so issues are caught before a commit or PR. ## Core Features & Use Cases - Five-axis critique: Evaluates changes on abstraction level (preferring engine APIs over reinvention), Doc/code data boundaries, test strategy alignment, readability, and beginner-friendliness of the code structure. - Diff or module targeting: Reviews the current git diff by default, or a specified file or module, cross-referencing the engine's module index to detect reinvented wheels. - Report-only output: Returns a prioritized list of findings with file and line references plus fix suggestions, without modifying code itself. - Use Case: After implementing a new game feature in the Flix engine, run the critique before reporting completion to catch hardcoded UI strings, missing tests for new rules, or low-level API calls that should use higher-level modules. ## Quick Start Ask the AI to critique the current uncommitted changes with the critique-code skill and return the five-axis report before committing.
