roblox-code-review
installsforks
How to install roblox-code-review?
tabooharmony/roblox-brain/roblox-code-review
$npx -y skills add TabooHarmony/roblox-brain --skill roblox-code-reviewUse when reviewing Roblox or Luau code for security, performance, monetization, data persistence, or architecture risks.
SKILL.md
| 1 | # Code Review |
| 2 | |
| 3 | Review Roblox projects with security, performance, and monetization lenses. Apply relevant lenses based on what changed — not all every time. |
| 4 | |
| 5 | ## When to Load |
| 6 | |
| 7 | - User asks for code review on Roblox/Luau code |
| 8 | - User asks to audit security, performance, networking, monetization, or data persistence |
| 9 | - User asks about Roblox best practices for remotes, data saving, or code organization |
| 10 | |
| 11 | ## Quick Reference |
| 12 | |
| 13 | ### 8-Step Review |
| 14 | 1. **Project Scan** — scripts, folders, naming, Rojo/Wally/Studio |
| 15 | 2. **Organization** — correct services, PascalCase modules, no orphans |
| 16 | 3. **Code Quality** — `wait()`→`task.wait()`, `spawn()`→`task.spawn()`, globals |
| 17 | 4. **Architecture** — single responsibility, no circular requires, server/client split |
| 18 | 5. **Security** — validate remotes server-side, no client-trusted state, rate-limit |
| 19 | 6. **Performance** — consolidate Heartbeat, cache services, disconnect events |
| 20 | 7. **Report** — Grade A-F. Severity: Critical/High/Medium/Low |
| 21 | 8. **Refactor** — Immediate → Short-term → Long-term |
| 22 | |
| 23 | ### Routing — Load These Skills for Each Lens |
| 24 | |
| 25 | | Lens | Load | |
| 26 | |------|------| |
| 27 | | Gotchas & footguns | `roblox-sharp-edges` | |
| 28 | | Security audit | `roblox-security` | |
| 29 | | Remote validation | `roblox-networking` | |
| 30 | | Data persistence | `roblox-data` | |
| 31 | | Monetization | `roblox-monetization` | |
| 32 | | Performance | `roblox-performance` | |
| 33 | | Luau correctness | `roblox-luau-core`, `roblox-luau-types` | |
| 34 | |
| 35 | ### Output Format |
| 36 | 1. READY / NOT READY |
| 37 | 2. Critical blockers |
| 38 | 3. Warnings |
| 39 | 4. Pass count/% |
| 40 | 5. Failed items + fixes |
| 41 | |
| 42 | 📖 Full reference: `references/full.md` |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
