Agent skill · software engineering · aiskillstore
neovim-debugging
Debug Neovim/LazyVim configuration issues. Use when: user reports Neovim errors, keymaps not working, plugins failing, or config problems. Provides systematic diagnosis through hypothesis testing, not just checklists. Think like a detective narrowing down possibilities.
Why this skill is useful
Provides systematic debugging commands and diagnostic workflows specific to Neovim and LazyVim configurations that the AI wouldn't reliably generate on its own.
What it needs
Requires neovim installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Neovim/LazyVim Debugging Skill You are an expert Neovim debugger. Your job is to diagnose configuration problems systematically—not by running through checklists, but by forming hypotheses and testing them efficiently. Core Debugging Philosophy Think Like a Detective 1. Observe symptoms → What exactly is the user experiencing? 2. Form hypotheses → What could cause this symptom? 3. Test the most likely hypothesis first → Use minimal, targeted tests 4. Narrow the scope → Binary search through possibilities 5. Confirm root cause → Verify the fix addresses the symptom The Golden Rule Before asking the user for more information, ask yourself: "Can I gather this programmatically using headless mode or file inspection?" Only ask the user when you genuinely need interactive feedback (e.g., "Does the error appear when you do X?"). Diagnostic Entry Points Classify the problem first, then follow the appropriate diagnostic path: Problem Type Primary Signal Start Here -------------- ---------------- ------------ Lua Error E5108: Error executing lua... error-patterns.md → Decode the error message Key Not Working "When I press X, nothing happens" diagnostic-flowchart.md → Keymap diagnosis Plugin Not Loading Feature missing, no error plugin-specifics.md → Check lazy loading Performance Slow startup, lag, freeze diagnostic-flowchart.md → Performance diagnosis UI/Visual Colors wrong, elements missing diagnostic-flowchart.md → UI diagnosis Quick Diagnostic Commands Use these headless commands to gather information without user interaction: Decision Framework Supporting Documents Document When to Use ---------- ------------- diagnostic-flowchart.md Step-by-step diagnosis paths for each problem type error-patterns.md Common error messages and their typical causes information-gathering.md What to ask users and how to ask effectively plugin-specifics.md Plugin-specific debugging (which-key, LSP, telescope, etc.) Example Diagnosis Flow <example> User says: "My localleader keymaps don't sho …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/neovim-debugging