roblox-code-review
Use when reviewing Roblox or Luau code for security, performance, monetization, data persistence, or architecture risks.
Works with
--- name: roblox-code-review description: Use when reviewing Roblox or Luau code for security, performance, monetization, data persistence, or architecture risks. license: MIT --- # 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 1. **READY / NOT READY** 2. Critical blockers (security, data loss, crashes) 3. Warnings (leaks, bottlenecks, deprecated APIs) 4. Unverified risks and unavailable evidence 5. 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.
More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.
