analyze

Investigate complex Roblox Luau codebase behaviors using read-only repository analysis to trace causality and architectural tradeoffs. This provides ranked, evidence-based explanations for system impacts, ensuring non-speculative output by strictly separating hard file evidence from logical inference.

Evidence-based codebase analysis for Roblox plugins is a structured investigation method that explicitly labels findings as either hard evidence or logical inference. It traces logic across multiple modules to identify causality and architectural tradeoffs, preventing speculative debugging.

Find the cause of a remote validation failure by tracing the logic across multiple Roblox plugin modules. This yields a ranked list of likely causes based on actual file evidence, explicitly mapped to distinguish verified facts from inferred explanations.

Yes, you can examine data store regressions in Roblox Studio by analyzing relevant provider contracts and remote schema files. The skill operates across Studio artifacts to identify system impacts and provide grounded synthesis of the regression's root cause.

The limitation of evidence-vs-inference reporting is that it operates strictly read-only, meaning it cannot modify or execute code to test hypotheses. It relies entirely on examining existing artifacts to provide high-confidence explanations, explicitly avoiding speculative conclusions.