跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

roblox-code-review

Use when reviewing Roblox or Luau code for security, performance, monetization, data persistence, or architecture risks.

TabooHarmony · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add TabooHarmony/roblox-brain --skill roblox-code-review

技能说明


name: roblox-code-review description: "Use when reviewing Roblox or Luau code for security, performance, monetization, data persistence, or architecture risks." last_reviewed: 2026-08-07 sources: [original] kind: router

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

LensLoad
Security auditroblox-security
Remote validationroblox-networking
Data persistenceroblox-data
Cross-server stateroblox-server-data
Monetizationroblox-monetization
Performanceroblox-performance
Luau correctnessroblox-luau-core, roblox-luau-types
Architectureroblox-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.