neovim-debugginglisted

# 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](error-patterns.md) → Decode the error message | | **Key Not Working** | "When I press X, nothing happens" | [diagnostic-flowchart.md](diagnostic-flowchart.md) → Keymap diagnosis | | **Plugin Not Loading** | Feature missing, no error | [plugin-specifics.md](plugin-specifics.md) → Check lazy loading | | **Performance** | Slow startup, lag, freeze | [diagn