Roblox Code Review
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
require calls, 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.
1---2name: roblox-code-review3description: "Use when reviewing Roblox or Luau code for security, performance, monetization, data persistence, or architecture risks."4last_reviewed: 2026-08-075sources: [original]6kind: router7---89# Roblox Code Review1011Route 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.1213## When to Load1415- User asks for code review on Roblox/Luau code16- User asks to audit security, performance, networking, monetization, or data persistence17- User asks about Roblox best practices for remotes, data saving, or code organization1819## Quick Reference2021### Routing: Load These Skills for Each Lens2223| Lens | Load |24|------|------|25| Security audit | `roblox-security` |26| Remote validation | `roblox-networking` |27| Data persistence | `roblox-data` |28| Cross-server state | `roblox-server-data` |29| Monetization | `roblox-monetization` |30| Performance | `roblox-performance` |31| Luau correctness | `roblox-luau-core`, `roblox-luau-types` |32| Architecture | `roblox-architecture` |3334### Static-Analysis Limits3536- Static scans can flag numeric `require` calls, dynamic-code markers, obfuscation-like names, cleanup tokens, and duplicate files; these are provenance or review signals, not verdicts.37- Trace the containing function, authority boundary, reachability, and lifecycle before assigning severity.38- Label search-only findings separately from observed runtime behavior, test results, and unavailable evidence.39- **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.4041### Output Format42431. **READY / NOT READY**442. Critical blockers (security, data loss, crashes)453. Warnings (leaks, bottlenecks, deprecated APIs)464. Unverified risks and unavailable evidence475. Findings with specific fixes4849Severity: 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.