Menu
Review Luau code for style compliance, type safety, server authority, error handling, and performance. Use for reviewing a file, a PR-sized change, or a whole module.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run a comprehensive health check on the repo. Verifies README counts match reality, promised files exist, no unresolved placeholders, wiki index is synced, toolchain configs are valid, and agent roster is accurate. Use after making structural changes or before publishing.
Begin a new Roblox game project or onboard to an existing one. Use when starting a fresh session with no context, or when the user says "let's start" or "new project".
Generate a 3D asset from a reference image using Blender MCP's image-to-3D AI (Hyper3D). Optimizes for Roblox and exports FBX.
Generate a 3D asset for Roblox using Blender MCP. Creates models from text descriptions via AI (Hyper3D/Hunyuan3D) or downloads from PolyHaven/Sketchfab, optimizes for Roblox constraints, and exports FBX.
Inspect the current Roblox Studio state via MCP. Verifies instance hierarchy, checks for common structural issues, and reports findings.
Capture a screenshot of the current Roblox Studio viewport and analyze it. Use for visual verification of UI, lighting, level layout, and general game appearance.
| name | code-review |
| description | Review Luau code for style compliance, type safety, server authority, error handling, and performance. Use for reviewing a file, a PR-sized change, or a whole module. |
Ask the user:
git diff HEAD~1 or git diff main...HEAD stylelocal Module = {} ... return Modulelocal Players = game:GetService("Players")print() left in production code (unless behind a debug flag)wait(), spawn(), delay() — should use task.wait(), task.spawn(), task.defer()pcallMarketplaceService.ProcessReceipt server-sideworkspace.X lookups)table.concat)# Code Review: [Scope]
## Summary
- Files reviewed: X
- Critical issues: X
- Important issues: X
- Suggestions: X
## Critical (must fix before merge)
1. **[filepath:line]**: [issue]
- Reason: [why it's critical]
- Fix: [specific code change]
## Important
...
## Suggestions
...
## Kudos
- [Things done well — reinforce good patterns]
Present the review to the user. Never apply fixes without approval. Offer to delegate fixes to the appropriate specialist.