# GS Code Reviewer: A Clear Verdict on Every Code Change > The GS Code Reviewer is the Luau code review seat in your Roblox game studio on the Ai1 platform by MyZone AI: it checks every change against the plan, the coding standard and a Roblox checklist, and returns approve or changes requested with a file and line for every finding. Canonical page: https://myzone.ai/pages/agents/ai-game-studio-reviewer-agent Part of Ai1, by MyZone AI. Book a code review walkthrough: https://calendly.com/d/ct6h-tcy-8qf/ai1-demo?a1=GS%20Code%20Reviewer&utm_source=myzone.ai&utm_medium=agent-page&utm_content=ai-game-studio-reviewer-agent-final Last updated: 2026-10-05. Reviewed by the MyZone AI team. A clear verdict on every code change, with a file and line for each finding. ## At a glance - **How you use it:** The learner asks GS Producer, which passes each change here with its ticket and plan - **What it checks:** Server control, message checks, saving, secrets, tests, performance and lint - **Every finding:** Severity, file and line, what is wrong, why it matters and how to fix it - **What it judges:** Only the evidence in the change, never the builder's own summary - **Repair round:** One, then a recheck; a second rejection goes back to GS Producer - **What it never does:** Write the fix, playtest, merge or publish ## What the GS Code Reviewer does - **Reviews with fresh eyes:** Each review starts from a clean slate, kept separate from the seat that built the change. - **Works from a Roblox checklist:** It checks the change against the technical plan, the coding standard and a Roblox checklist: server control, message checks, saving, secrets, tests, performance and lint results. - **Findings you can act on:** Every finding states its severity, the file and line, what is wrong, why it matters and how to fix it. - **Guards tests and requirements:** If a change edits an existing test or requirement, that is a critical finding, and a critical finding always means changes requested. - **Rechecks the repair:** After the single repair round, it reviews again and closes or keeps each original finding. ## How the GS Code Reviewer differs from a builder checking its own work A builder checking its own work tends to see what it meant to write. The GS Code Reviewer starts from a clean slate, judges only the evidence in the change and works through a Roblox checklist covering server control, saving, secrets, tests and performance. Every finding comes with a file and line, any edit to an existing test is critical, and after one repair round a second rejection goes back to GS Producer. How this differs from the GS Playtester (https://myzone.ai/pages/agents/ai-game-studio-playtester-agent): GS Playtester proves a build works, requirement by requirement, while GS Code Reviewer checks the code itself before that build reaches testing. ## How it works 1. **Change in** (When a builder hands back): GS Producer passes over the change together with its ticket, the plan and the evidence. 2. **Review** (With every change): It checks the change against the plan, the coding standard and the Roblox checklist. 3. **Verdict** (After each review): It returns approve, or changes requested with a clear list of findings. 4. **Recheck** (After the one repair round): The one repair round is reviewed again. A second rejection stops that work and returns it to GS Producer. ## When to use it - **A builder hands back a new gameplay change:** It reviews the change and approves it, listing the evidence it checked. - **A shop change trusts the price a player sends:** It raises a critical finding, asks for changes and points to the exact file and line with how to fix it. - **A change quietly edits an existing test:** It treats the edit as critical and asks for changes, so tests and requirements stay as agreed. - **The repair for earlier findings is in:** It runs a second review that closes or keeps each original finding. ## What you get - A code review verdict for each change: approve or changes requested - Findings with severity, file and line, what is wrong, why and how to fix it - The evidence it checked to reach the verdict - A recheck after the repair round that closes or keeps each finding ## Example: Code review of a shop purchase change Example with a fictional company. Names, people and figures are invented to show the agent's output. Any resemblance to a real company or person is unintended. Industry facts are real and cited with their sources. What it was asked: Review the tackle shop purchase change, then check the repair when it comes back. An invented code change for an invented game was reviewed the way GS Code Reviewer works today: the change, ticket, technical plan, test results and lint results arrive from GS Producer, and each line of the Roblox review checklist is answered from that evidence, never from the builder's summary. Nothing was run in Roblox Studio or a live game, no playtest was done, nothing was merged or published, and no player data was read. Run date: 1 October 2026. ### What it found - The first review requested changes: the tackle shop charged whatever price the player's device sent, so a cheater could get the best rod for 0 coins. - The coin save was not wrapped in a safe call with retries, so a failed save could lose a player's coins or their new rod. - After the one allowed repair round, all five findings that blocked approval were closed with test and lint evidence, so the change was approved; one low style note stays open. ### Sources - [Security and cheat mitigation tactics | Documentation - Roblox Creator Hub](https://create.roblox.com/docs/scripting/security/security-tactics), Roblox Creator Hub (accessed 2026-10-01) - [Data store error codes and limits | Documentation - Roblox Creator Hub](https://create.roblox.com/docs/cloud-services/data-stores/error-codes-and-limits), Roblox Creator Hub (accessed 2026-10-01) ## Guardrails - It judges only the evidence in the change, never the builder's summary of it. - Any edit to an existing test or requirement is a critical finding, and a critical finding always means changes requested. - It explains what needs fixing but never writes the fix, and offers no more than one line of replacement code. - There is one repair round. A second rejection stops that piece of work and sends it back to GS Producer for a decision. - Until your Ai1 team sets up the studio profile, the studio gives general Roblox help only and keeps no notes about the learner. ## Frequently asked questions ### What belongs on a Roblox code review checklist? Server control, checks on every message from a player's device, safe saving, secrets, tests, performance and lint results. The GS Code Reviewer in Ai1 by MyZone AI answers each line from the evidence in the change, most serious first, and ties every finding to a file and line. Each change is also checked against the technical plan and the coding standard. ### What does a changes requested verdict mean in code review? The change cannot be accepted yet. Every finding states its severity, the file and line, what is wrong, why it matters and how to fix it, and a builder makes the fix in one repair round. Anything that breaks safety or trust, including any edit to an existing test or requirement, is critical and always means changes requested. If a repair is rejected a second time, that piece of work stops and goes back to GS Producer, which decides what happens next. ### Which game code security slips can a code review catch? Common ones are a server that trusts a price sent by the player's device and a save with no retries. The GS Code Reviewer checks server control, saving and secrets while the change is still in review, where slips are cheapest to fix and before any player sees them. It explains the problem and what needs to change, but the fix is written by a builder. At most it offers a single line of replacement code. ### Is the GS Code Reviewer a general purpose code reviewer? No. It is a seat inside your Roblox game studio, part of it from the very first game. It reviews against the studio's plan and Roblox checklist and allows one repair round. The learner cannot send code to it directly. The learner talks only to GS Producer, which passes the change here and brings the verdict back. ## About Ai1 Ai1 is the AI operations platform by MyZone AI, where each client runs on its own private server. The GS Code Reviewer is not sold on its own: every Ai1 agent, including this one, is included on Developer Pro and every Fully Managed option, with no per-agent charge. Developer Core includes the development agents. Pricing: https://myzone.ai/pages/services/ai1-pricing. Security: https://myzone.ai/pages/security.