review-game

To review game codebase architecture, you can analyze the code, dependencies, and entry points to validate patterns like EventBus, GameState singletons, and orchestrator classes for structural quality and performance bottlenecks.

Yes, this game code review tool works with Three.js, Phaser, and other game engines by analyzing the project directory structure, dependencies, and code entry points to assess architecture and code quality.

A game codebase review should check for a centralized EventBus, a GameState singleton, centralized Constants, an orchestrator Game class, consistent event naming, and robust error handling to ensure maintainability.

No, a read-only game code review does not modify your existing source files. It performs a static analysis of the codebase to identify architectural and performance issues and outputs a structured assessment.

You should run an architecture quality review on your game project before a major refactor or release to receive a structured assessment of code structure, module boundaries, and prioritized recommendations.

The best way to identify performance bottlenecks in game code is to run a static analysis that checks for common resource management issues, maintainability signals, and architectural flaws like missing orchestrator classes.