y3-lua-review

Audit Lua code for API misuse, event errors, and syntax issues.

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/y3-editor/y3-maker-config --skill y3-lua-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: y3-lua-review
Source: https://github.com/y3-editor/y3-maker-config/tree/main/skills/y3-lua-review
Command: npx skills add https://github.com/y3-editor/y3-maker-config --skill y3-lua-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Y3 Lua Review systematically audits Lua code across game projects to detect and fix API misuse, event parameter errors, and syntax issues, delivering structured guidance and, where possible, deterministic fixes.

Core Features & Use Cases

  • Phase-driven workflow: four phases (scope, syntax, API/event compliance, and final reporting) to ensure thorough coverage.
  • API and event compliance: verifies API calls against references and source, validates event names and parameters.
  • Safe, deterministic fixes: applies only known, safe replacements to reduce manual rework in existing codebases.

Quick Start

Run the Lua review against your project to begin a four-phase audit and apply deterministic fixes where possible.

Frequently Asked Questions about y3-lua-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my Lua code for API misuse and event parameter errors in game development?

To audit Lua code for API misuse and event parameter errors, run a systematic static analysis that validates API calls against references and checks event names, applying deterministic fixes where possible across your game project.

What is the best way to identify syntax issues and known problem patterns in an existing Lua codebase?

The best way to identify syntax issues and known problem patterns in an existing Lua codebase is a four-phase static analysis workflow, progressing from project scope definition to syntax checking, API compliance, and a final report.

Can I automatically fix Lua API compliance issues and event handling traps during a code review?

You can automatically fix Lua API compliance issues and event handling traps during code review by applying known, safe replacements that deliver deterministic fixes, reducing manual rework in your game project.

Does Lua static analysis work for existing game projects to validate event names and parameters?

Lua static analysis works for existing game projects by systematically validating event names and parameters, checking type handling for known API traps, and ensuring API existence against source references.

What are the limitations of applying deterministic fixes during a Lua code review?

The limitation of deterministic fixes during a Lua code review is that the system only applies known, safe replacements to reduce manual rework, meaning complex or undocumented API misuse may still require manual intervention.