Menu
Format Lua files after editing. Apply when writing or modifying any .lua file.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Scaffold a new helper script in local/bin/ with proper boilerplate, msgr sourcing, and documentation tag.
Scaffold a bats test file in tests/<script>.bats matching a script in local/bin/<script>. Use when adding tests for an existing script that lacks coverage.
Scaffold a new theme handler in config/theme/handlers.d/<app>. Use when adding dark/light theme support for an app the orchestrator does not yet flip.
Validate fish scripts after editing. Apply when writing or modifying any .fish file in config/fish/.
Scaffold a new fish function in config/fish/functions/ with proper conventions and event handling.
| name | lua-format |
| description | Format Lua files after editing. Apply when writing or modifying any .lua file. |
| user-invocable | false |
| allowed-tools | Bash |
After editing any .lua file, format it with stylua:
stylua <file>
Project settings are in stylua.toml (90-char line length).
If stylua is not available, skip formatting silently.
config/nvim/ managed by plugins (lazy.nvim lockfile)