best-practicelisted

> **Script path fallback**: qq scripts are invoked as bare commands (e.g. `unity-test.sh`). If "command not found", use `${CLAUDE_PLUGIN_ROOT}/bin/<command>` instead. Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Quick best-practice check for Unity C# code. Run this right after editing code — it scans for anti-patterns, performance traps, and runtime safety issues against 18 rules. Arguments: $ARGUMENTS ## Scope Detection Intelligently determine what to check: 1. **If the user specified files or a scope** → use that 2. **If .cs files were edited in this conversation** → check those files 3. **If there are uncommitted changes** → `git diff --name-only HEAD -- '*.cs'` 4. **If none of the above** → ask the user what to check Do NOT review the entire codebase by default. Focus on what just changed. ## Review Rules ## Deterministic Policy Layer If `qq-policy-check.sh` is available, run it first against the selected scope: ```bash qq-policy-check.sh --json <files...> ``` Treat those results as the first-pass findings. Do not ask the model to rediscover the same high-confidence issues from scratch. Use the model for: - additional contextual review - prioritization - explanation - fix suggestions ### Anti-Pattern Detection 1. **FindObjectOfType / FindObjectsOfType** - Severity: High - Alternative: use the appropriate Registry/Manager singleton for your project - Exception: Edito