code-review

Game code review checks dependency direction, layer separation, and SOLID adherence to prevent regressions. It evaluates method design, complexity thresholds, and architectural alignment, emitting a structured verdict with required changes before code ships.

Checking ADR compliance scans game code files for architectural decision references and flags violations or drift. The review evaluates circular dependencies, event usage, and layer separation, returning a structured verdict with severity levels.

Detecting performance risks in game code involves reviewing delta-time usage, hot-path allocations, cleanup, and thread-safety. A structured review identifies these performance issues alongside testability and SOLID compliance, returning a verdict with required changes.

Evaluating testability in UI and engine-adjacent changes involves reviewing method and class design for complexity and size thresholds. The review ensures maintainability and alignment with project decisions, producing a structured verdict with required changes.

Running an architectural code review on a file or directory requires passing the target path as an argument. The review loads files, checks ADR compliance, runs parallel specialist reviews, and emits a structured verdict with required changes.