Route a Roblox code review to the right domain skills and produce a structured report. Apply relevant lenses based on what changed, not all every time.
When to Load
- User asks for code review on Roblox/Luau code
- User asks to audit security, performance, networking, monetization, or data persistence
- User asks about Roblox best practices for remotes, data saving, or code organization
Quick Reference
Routing: Load These Skills for Each Lens
| Lens | Load |
|---|---|
| Security audit | roblox-security |
| Remote validation | roblox-networking |
| Data persistence | roblox-data |
| Cross-server state | roblox-server-data |
| Monetization | roblox-monetization |
| Performance | roblox-performance |
| Luau correctness | roblox-luau-core, roblox-luau-types |
| Architecture | roblox-architecture |
Static-Analysis Limits
- Static scans can flag numeric
requirecalls, dynamic-code markers, obfuscation-like names, cleanup tokens, and duplicate files; these are provenance or review signals, not verdicts. - Trace the containing function, authority boundary, reachability, and lifecycle before assigning severity.
- Label search-only findings separately from observed runtime behavior, test results, and unavailable evidence.
- Vertical slice review: For a player-facing change, trace input → UI/world feedback → remote or simulation → authoritative state → persistence → cleanup. Review the real path; file or class co-occurrence is not proof that a runtime connection exists.
Output Format
- READY / NOT READY
- Critical blockers (security, data loss, crashes)
- Warnings (leaks, bottlenecks, deprecated APIs)
- Unverified risks and unavailable evidence
- Findings with specific fixes
Severity: Critical / High / Medium / Low. For each finding: file + line, what's wrong, impact, and the smallest correct fix. The routed domain skill owns detailed checks.