Reviewer: read-only AI code review for Verse and UEFN assets
The Reviewer is your team’s independent pair of eyes. It performs AI Verse code review and asset review in read-only mode: it inspects, reasons and reports, and never changes your project or remote services.
Independent AI Verse code review
The Reviewer checks code, assets, permissions, integration and release evidence in your UEFN (Unreal Editor for Fortnite) project without touching files, levels, wiring or remote tasks. It prioritizes substantiated defects over style remarks.
It traces behavior end to end and looks for concrete problems: reproducible errors, data loss, permission bypasses, shared-state mistakes, race and lifetime issues, broken asset references, performance regressions and unsupported API assumptions.
How it works
- Scope: it reads the requested scope, the relevant files and their callers, recorded tool results and genuinely read-only editor queries.
- Trace: it follows the behavior end to end, without assuming a Git or changeset tool exists.
- Evidence: it compares the implementation and tests with the requested behavior, and checks that a claimed build, export, import, render or gameplay result is backed by real output. A successful tool call can still leave the actual operation unsuccessful.
- Report: it ranks defects by impact, with the affected file or asset, the trigger, the consequence and a short proposed fix.
It relies on the pilot-review and pilot-qa Skills, then on the Skill for the domain under review. It often checks work from the Verse Coder or the NPC Author, complements the Tester’s evidence and can be called by the orchestrator before a release.
Example prompts
- Review the shop system before release.
- The Verse Coder reports a successful build: check that it is backed by output.
- Look for data loss risks in how coins are saved.
- Does the round manager have race or lifetime issues?
- Check that no level asset reference broke after the rename.
Tools and connections
- Access
- read-only: no file writes and no image generation
- Connections
- UEFN and Blender, for inspection only
- Starting Skills
- pilot-review, pilot-qa
- Report
- confirmed defects, open questions and checks not performed
- Works with
- Verse Coder, NPC Author, Tester, Orchestrator
Limits
The Reviewer keeps to its read-only boundary even when a Skill describes a repair procedure: no file writes, image or 3D generation, Blender execution, builds, wiring, placement or remote deletion, and no working around a denied tool through another interface. When it finds no defect, it states what it inspected and what remains to validate: a limited review is not proof that everything works.
For the code side, see Verse code; to get started, see pricing.
FAQ
Can it fix what it finds?
No. It proposes a short fix for each defect and leaves the implementation to a task that is allowed to edit, such as the Verse Coder.
Why a read-only agent?
To keep the review independent from the work it assesses: the Reviewer finds and documents, then a specialist allowed to edit makes the fix. Its findings stay evidence you can hand to the right agent.
Does a clean review mean everything works?
No. The Reviewer states the scope it inspected and the validation still needed. In-game behavior is confirmed by real checks, such as the Tester’s, or by your own playtests.