lua-lint

Run StyLua formatting checks and Luacheck linting on Lua files.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/khwerhahn/okuban.nvim --skill lua-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lua-lint
Source: https://github.com/khwerhahn/okuban.nvim/tree/main/.claude/skills/lua-lint
Command: npx skills add https://github.com/khwerhahn/okuban.nvim --skill lua-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure consistent Lua code formatting and catch common code issues automatically, removing the need for manual style checks and ad-hoc lint runs before commits or during reviews.

Core Features & Use Cases

  • StyLua formatting checks: Perform dry-run checks to find formatting mismatches and optionally auto-fix style issues.
  • Luacheck linting: Run static analysis to surface warnings and errors grouped by file to speed debugging.
  • Use Case: Run before committing or in CI to enforce style and quality, or run on a single file when iterating on a change.

Quick Start

Run the lua-lint skill to check and report formatting and linting for the repository or provide a specific file path as an argument.

Frequently Asked Questions about lua-lint

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

FAQPage Schema
How do I run Lua linting and formatting checks before committing code?

You can format and lint Lua files by running the skill with an optional file-or-directory argument. It applies StyLua formatting checks and Luacheck linting to the specified path, outputting per-file reports for styling mismatches and code issues.

What does Luacheck static analysis detect when validating Lua source code?

Luacheck linting surfaces warnings and errors grouped by file to speed debugging. It performs static analysis on Lua source files to catch common code issues, which helps enforce code quality during developer workflows or before commits.

Do I need StyLua and Luacheck installed to format and lint Lua files?

Yes, the skill requires both StyLua and Luacheck to be installed in your environment. These dependencies are necessary to execute the formatting checks and linting operations on your Lua source files.

Can I target a single Lua file for formatting and linting instead of an entire directory?

Yes, the skill accepts an optional file-or-directory argument for targeted checks. You can provide a specific Lua file path to run StyLua and Luacheck on a single file, or specify a directory to validate the entire project.

What is the best way to enforce consistent Lua code quality in a CI pipeline?

Running automated StyLua formatting checks and Luacheck linting in CI is the best way to enforce Lua code quality. The skill generates per-file formatting and lint reports, removing the need for manual style checks and ad-hoc runs during CI pipelines.

Are there limitations when using StyLua dry-run checks for Lua formatting mismatches?

StyLua dry-run checks identify formatting mismatches in Lua code but do not automatically apply fixes in the standard report. The skill detects styling mismatches and optionally auto-fixes style issues, requiring manual intervention for complex linting warnings.