code-review

Automated code reviews for SOLID principles evaluate source files to detect violations, verify dependency direction, and check cyclomatic complexity. They report findings without modifying any files.

Architectural code review examines software structure to ensure proper dependency direction and avoid circular dependencies. It validates compliance with SOLID principles, coding standards, and architectural decision records.

Yes, static analysis and code reviews apply to game engine source files. They validate game-specific performance considerations like frame-rate independence, hot-path allocations, and resource cleanup alongside standard architectural checks.

Reviewing code for ADR alignment and coding standards compliance involves analyzing source files to ensure decisions match recorded ADRs. The process checks line limits, cyclomatic complexity, and dependency injection rules.

The best way to check game code for hot-path allocations and frame-rate independence is through specialized architectural code review. It spawns parallel engine specialists to provide focused feedback on performance and resource cleanup.

No, the code review process does not modify source files during static analysis. It analyzes code structure, detects violations across multiple dimensions, and reports findings to ensure technical debt is identified safely.