code-review

Reviews game code files for standards, SOLID principles, ADR compliance, and testability.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill code-review-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/code-review
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill code-review-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game projects accumulate architectural drift and untestable code when reviews are inconsistent. This Skill runs a structured, multi-phase review of implementation files against coding standards, architecture decision records, and game-specific performance concerns, producing a clear approval verdict. ## Core Features & Use Cases - ADR Compliance Checking: Locates referenced architecture decision records from story files, header comments, or git history and classifies deviations as violations, drift, or minor issues. - Parallel Specialist Reviews: Spawns engine, language, shader, UI, and QA testability specialists concurrently via subagents and aggregates their findings. - Structured Verdict Output: Produces a standardized review report covering standards, SOLID, game-specific concerns like frame-rate independence and hot-path allocations, ending in APPROVED or CHANGES REQUIRED. - Use Case: After implementing a combat system story in a Godot project, run the review on the new .gd files with the story path to verify ADR compliance and testability before marking the story done. ## Quick Start Ask the AI to run the code-review skill on your recently changed implementation files, optionally passing the related story file so ADR compliance can be checked.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a code review on game implementation files?

Invoke the code-review skill with the target file paths as arguments, optionally appending the story file path. The skill reads the files, checks standards and architecture, spawns specialist reviewers, and returns a structured verdict report.

How does ADR compliance checking work in a code review?

The skill searches the story file, header comments, and git history for ADR references, then reads each ADR's Decision and Consequences sections. Deviations are classified as architectural violations, ADR drift, or minor deviations with blocking or warning severity.

Does this code review skill modify my source files?

No, the skill is explicitly read-only and writes no files. It only reads implementation files, project configuration, and ADRs, then outputs a review report with required changes and suggestions.

What happens if no engine is configured for the project?

If the Engine Specialists section in project.json reads [TO BE CONFIGURED], the skill skips engine specialist reviews and notes this in the output. Standards, SOLID, and game-specific checks still run normally.

What game-specific issues does the review check for?

The review checks frame-rate independence through delta time usage, allocations in hot paths like update loops, null and empty state handling, thread safety, and resource cleanup to prevent leaks.