From blueprint
Read-only gap analysis comparing a Neovim Lua plugin's current quality setup against the 9-dimension methodology. Use when user says "audit quality", "check coverage gaps", "what's missing", or wants to see how their Neovim plugin measures up before running setup.
How this skill is triggered — by the user, by Claude, or both
Slash command
/blueprint:nvim-lua-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read-only — does not modify any files.
Read-only — does not modify any files.
Read these files before starting:
skills/shared/references/audit-workflow.md — the 5-step workflow structureskills/nvim-lua-setup/references/methodology.md — the 9 quality dimensions (roles) to audit againstskills/nvim-lua-setup/references/analysis-checklist.md — what to check in the target codebaseFollow audit-workflow.md. Neovim Lua-specific details:
Detect project structure (lua/, plugin/, tests/, doc/), plugin type, test framework (plenary/mini.test/busted). Inventory existing configurations in selene.toml, .stylua.toml, .luacov, .luarc.json. Check hooks, CI, installed tools.
Check each of the 9 dimensions — see methodology.md for Neovim Lua-specific tools and thresholds.
Expected hooks: SessionStart (plugin structure check), PostToolUse/Edit|Write (StyLua), Stop (quality gate), PostToolUse/Bash (semver check).
Expected jobs: test (Neovim matrix), lint (selene + stylua), typecheck (optional), version.
Present dimension/hook/CI coverage tables with recommendations. Suggest running /blueprint:nvim-lua-setup to configure missing dimensions.
No lua/ directory found: The project may not be a Neovim plugin. Suggest using the appropriate blueprint skill instead.
npx claudepluginhub ondrasek/cc-plugins --plugin blueprintApplies Neovim community best practices, plugin architecture patterns, and idiomatic Lua style when writing, reviewing, or refactoring Neovim plugins.
Validates, audits, and improves Neovim config (lazy.nvim, GNU Stow). Add plugins, diagnose issues, fix keymaps, and apply best practices.
Audits Claude Code plugins for security vulnerabilities, best practices, CLAUDE.md compliance, marketplace readiness, git hygiene, performance, and UX. Produces scored reports using scans for secrets, dangerous commands, and structure validation.