neovim-config

Validate Neovim Lua configurations, plugin wiring, and startup behavior.

1|1|Updated May 3, 2026
One-click install
npx skills add https://github.com/matt-riley/agent-skills --skill neovim-config-matt-riley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neovim-config
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/neovim-config
Command: npx skills add https://github.com/matt-riley/agent-skills --skill neovim-config-matt-riley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Neovim configurations can be fragile across worktrees and plugin setups; this skill provides a structured approach to editing, debugging, and validating Neovim Lua configurations, including plugin management, LSP wiring, treesitter, statusline, and startup behavior.

Core Features & Use Cases

  • Validate and wire Neovim Lua configs (init.lua, lua/, plugin/, after/, ftplugin/).
  • Manage and validate plugin loading with vim.pack and lazy.nvim, including pinning and bootstrap checks.
  • Validate startup paths, LSP/treesitter integration, and statusline behavior across worktrees or isolated environments.

Quick Start

Launch the validation workflow on your Neovim checkout to verify correct config loading, plugin wiring, and startup behavior.

Frequently Asked Questions about neovim-config

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

FAQPage Schema
How do I validate my Neovim Lua config for plugin wiring and startup errors?

Validate Neovim Lua config by applying this skill to your checkout to verify plugin wiring, LSP setup, and startup behavior. It checks real TTY startup paths and isolated XDG configurations to identify configuration issues.

Can I use this to check lazy.nvim and vim.pack plugin loading in my Neovim config?

Yes, you can check lazy.nvim and vim.pack plugin loading. This skill validates plugin management, including pinning and bootstrap checks, to ensure your Neovim Lua configuration loads correctly across different plugin managers.

How do I test Neovim config across isolated environments and worktrees?

Test Neovim config across worktrees by applying this skill to verify correct config loading, plugin wiring, and startup behavior. It uses isolated XDG configurations to validate boundary conditions and ensure consistent LSP and treesitter integration.

What is the best way to debug LSP and treesitter integration in an init.lua file?

The best way to debug LSP and treesitter integration is using this skill to validate your init.lua and lua directory. It checks integration points and startup behavior to identify wiring issues within your Neovim configuration.

Does this Neovim config validation support ftplugin and after directory structures?

Yes, this Neovim config validation supports ftplugin and after directory structures. It identifies and validates configurations across init.lua, lua, plugin, after, and ftplugin directories to ensure proper loading and boundary validations.

Why does my Neovim config break when switching worktrees with different plugin setups?

Neovim configs break across worktrees due to fragile plugin setups. This skill provides structured validation of plugin management, LSP wiring, and startup behavior to identify and resolve these configuration inconsistencies.