code-review

Reviews Unity C# files for coding standards, architecture, SOLID principles, and performance issues.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/DJackyB/Project_Rent --skill code-review-djackyb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/DJackyB/Project_Rent/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/DJackyB/Project_Rent --skill code-review-djackyb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually checking code against project conventions, architecture rules, and Unity-specific pitfalls is slow and inconsistent. This Skill automates structured code review for Unity game projects, producing a standardized report with compliance scores and actionable findings. ## Core Features & Use Cases - Standards Compliance Checks: Verifies method length, cyclomatic complexity, documentation comments, dependency injection, and configuration sourcing against project rules. - Architecture & SOLID Audit: Validates dependency direction (Core ← GameFlow ← Board/Card/UI), EventBus-based communication, and all five SOLID principles. - Unity-Specific Inspection: Detects GetComponent calls in Update(), GC allocations in hot paths, incorrect null checks, coroutine leaks, and improper field visibility. - Use Case: Before merging a new card system feature, run the review on the changed directory to receive a scored report listing must-fix violations, optional suggestions, and a pass/fail conclusion. ## Quick Start Ask the AI to review a specific file or directory, for example: run a code review on Assets/Scripts/CardSystem and report any architecture or SOLID violations.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review Unity C# code for architecture violations?▼

Run the review on a target file or directory to check dependency direction, circular dependencies, and EventBus usage. The output report lists each architecture violation with its location and a pass/fail conclusion.

How to check SOLID principles in a Unity game project?▼

The review evaluates all five SOLID principles per class, including single responsibility, open-closed extensibility via factory patterns, and dependency inversion through interfaces. Violations are listed in a dedicated report section.

What Unity performance issues does a code review catch?▼

It detects GetComponent calls inside Update(), GC allocations from string concatenation or LINQ in hot paths, incorrect null checks on Unity objects, and coroutines without stop logic. These are reported in a Unity-specific section.

Can I review an entire directory instead of a single file?▼

Yes, the review accepts either a file path or a directory as its argument. It reads project conventions from the Doc/00_必读 directory first, then applies category-specific standards to each system found.

What coding standards are enforced during the review?▼

Checks include documented public APIs, methods under 40 lines, cyclomatic complexity under 10, dependency injection over direct Manager references, and configuration values sourced from GameConfig or ScriptableObject rather than hardcoded.