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.4---56# Roblox Code Review78Route 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.910## When to Load1112- User asks for code review on Roblox/Luau code13- User asks to audit security, performance, networking, monetization, or data persistence14- User asks about Roblox best practices for remotes, data saving, or code organization1516## Quick Reference1718### Routing: Load These Skills for Each Lens1920| Lens | Load |21|------|------|22| Security audit | `roblox-security` |23| Remote validation | `roblox-networking` |24| Data persistence | `roblox-data` |25| Cross-server state | `roblox-server-data` |26| Monetization | `roblox-monetization` |27| Performance | `roblox-performance` |28| Luau correctness | `roblox-luau-core`, `roblox-luau-types` |29| Architecture | `roblox-architecture` |3031### Static-Analysis Limits3233- 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.34- Trace the containing function, authority boundary, reachability, and lifecycle before assigning severity.35- Label search-only findings separately from observed runtime behavior, test results, and unavailable evidence.36- **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.3738### Output Format39401. **READY / NOT READY**412. Critical blockers (security, data loss, crashes)423. Warnings (leaks, bottlenecks, deprecated APIs)434. Unverified risks and unavailable evidence445. Findings with specific fixes4546Severity: 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.
tabooharmony