Code Review for Unreal Codebases

Code review in Unreal projects is different from code review in a typical web or backend codebase. The engine imposes conventions — UCLASS macros, reflected properties, module boundaries, Blueprint exposure patterns — that generic review tooling does not understand. A linter can catch a missing semicolon. It cannot catch a UPROPERTY with the wrong specifier that will silently break Blueprint access at runtime.

Standard code review tools operate at the file and function level. They see syntax, style, and basic patterns. They do not see module dependency boundaries, class hierarchy implications, or the relationship between C++ code and its Blueprint-facing surface. This gap means the most consequential review issues — the ones that cause runtime failures, asset pipeline breaks, or cross-module regressions — pass through undetected.

• Reflected property specifiers that compile but break Blueprint access
• Module dependency changes that create circular references downstream
• Class hierarchy modifications that invalidate assumptions in child Blueprints
• Config file changes that behave differently across build configurations
• Include order issues that only surface in Unity or Shipping builds

Gamibase Code Review uses the same Project Intelligence layer that powers Build Doctor and Crash Analysis. It knows your module graph, class hierarchy, and Blueprint exposure surface. When it reviews code, the suggestions are grounded in the actual project structure — not generic heuristics applied to isolated files.

# Review a specific path
gamibase review --path Source/MyModule/

# Review changes in the current branch
gamibase review --diff HEAD~1

Code Review does not suggest fixes, generate patches, or modify files. It produces findings — structured observations with context about why something matters and where the risk is. The operator reads the findings and decides what to do. This is not a limitation. It is the reason teams trust the output. A review tool that quietly rewrites code is not a reviewer — it is an editor with opinions.

Gamibase Code Review outputs structured findings that work in terminal, CI, and editor contexts. In CI, you can run it against a diff and post findings as PR comments. In VSCode, findings appear in the editor context. In the terminal, they render as readable text. The review content is identical across surfaces — only the presentation changes.