Codex Game Code Review for ADRs and Update-Loop Performance
Review game code against project standards and architecture decisions. Check dependency direction, UI state ownership, testability, and hot-path costs.
中文Install in Codex
Codex with a Codex-Code-Game-Studios checkout, target files, technical preferences, and any relevant ADRs.
- Open the pinned GitHub original and retain the complete `.agents/skills/code-review/` directory in the checkout.
- Open Codex in that checkout and invoke `$code-review` with the example task and desired output.
Example task
Invoke `$code-review` on two local UI components in a practice branch. Ask who owns the timer state and what stops updates when a panel closes.What to check
The review states who owns the state and when updates cease. Findings include file locations and concrete test coverage or gaps.
Original SKILL.md on GitHub · Updated
Frequently asked question
What if no ADR is referenced?
Record that no ADR was found for the diff, then review the project standards, actual dependencies, and tests.