skills.rest
tykisgod
tykisgodCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

codex-code-review

Automate Unity C# code review with Codex CLI and verified findings.

10|2|Updated Mar 28, 2026
Search Tags:#csharp#unity#code review#game dev#automated review#codex cli#code verification
One-click install
npx skills add https://github.com/tykisgod/quick-question --skill codex-code-review-tykisgod
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-code-review
Source: https://github.com/tykisgod/quick-question/tree/main/skills/codex-code-review
Command: npx skills add https://github.com/tykisgod/quick-question --skill codex-code-review-tykisgod

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires codex-cli, git, python.

What problem does it solve?

Manual code review for Unity C# game projects is slow, inconsistent, and often misses critical bugs, architecture violations, or performance issues, especially after large uncommitted changes or branch merges. This skill automates the entire review workflow using Codex CLI with a custom Unity 18-rule best-practice checklist, ensuring consistent, thorough reviews without manual effort, and automatically verifies every finding against live Unity Editor state to avoid false positives.

Core Features & Use Cases

  • Automated Code Review: Uses Codex CLI with high reasoning effort to review uncommitted changes, branch diffs against a base, or explicit file lists for Unity C# code, with a built-in Unity-specific best-practice checklist.
  • Iterative Review Loop: Automatically re-runs reviews until no critical issues remain (up to 5 rounds), intelligently handling over-engineering suggestions by prioritizing simpler, proportionate fixes.
  • Verified Findings Gate: Dispatches parallel subagents to verify every critical and moderate finding against live Unity Editor runtime state via tykit, not just static source code, and enforces a gate that blocks code edits until all verifications are complete.
  • Use Case: After running /qq:test and before committing code, use this skill to catch bugs, architecture issues, and performance problems in your Unity C# changes, with all confirmed issues fixed automatically and test failures handled with your input.

Quick Start

After writing C# changes for your Unity project, invoke the codex-code-review skill to automatically review uncommitted changes, verify all findings against the live Editor, and fix any critical issues before you commit to the branch.

Frequently Asked Questions about codex-code-review

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

FAQPage Schema
How do I automate Unity C# code review for uncommitted changes?▼

Automate Unity C# code review using Codex CLI with a custom 18-rule best-practice checklist to review uncommitted changes, branch diffs, or explicit file lists. It iteratively re-runs reviews until no critical issues remain before code commit.

How does automated code verification handle false positives in Unity?▼

Automated code verification dispatches parallel subagents to verify every critical and moderate finding against live Unity Editor runtime state via tykit. This prevents false positives by checking actual engine behavior rather than relying solely on static source code analysis.

Does the automated review require Codex CLI configuration and Unity Editor access?▼

Yes, automated review requires Codex CLI configuration and Python for execution, alongside access to the Unity Editor for runtime verification of findings via tykit. Git is also required to analyze uncommitted changes and branch diffs effectively.

What is the best way to enforce a code review gate before committing Unity C# scripts?▼

Enforce a code review gate by dispatching parallel subagents to verify all critical and moderate findings against live Unity Editor state. This gate blocks code edits until all verifications are complete and no critical issues remain.

Can I use this automated review to check branch diffs against a base branch?▼

Yes, automated review applies to checking branch diffs against a base branch for Unity C# codebases. It leverages Codex CLI with high reasoning effort to evaluate architectural violations and performance issues using a Unity-specific checklist.

Why does the iterative review loop stop after fixing critical Unity C# issues?▼

The iterative review loop stops after up to 5 rounds once no critical issues remain. It intelligently handles over-engineering suggestions by prioritizing simpler, proportionate fixes to ensure clean, efficient Unity C# code.

Related Skills

Explore More Software Engineering Skills→
rintirinti

code-review

Evaluate uncommitted git diffs with Codex CLI review feedback.

Community
Advanced
tykisgodtykisgod
10

claude-code-review

Automate iterative C# code reviews for Unity, Godot, Unreal, and S&box projects.

Community
Advanced
delorenjdelorenj
14

debugging-complex-multi-layer-systems

Diagnose multi-layer bugs with top-down fix order and isolation tests.

Community
Advanced
macaughmacaugh
5

Static Vulnerability Analysis

Detects injection, memory safety and authorization flaws in multiple languages.

Community
Advanced