Diagnose and repair Neovim/LazyVim plugin errors and startup issues.
npx skills add https://github.com/ivy/dotfiles --skill nvim-ivy
Please help me install this Agent Skill. Skill: nvim Source: https://github.com/ivy/dotfiles/tree/main/.claude/skills/nvim Command: npx skills add https://github.com/ivy/dotfiles --skill nvim-ivy
Use when troubleshooting Neovim/LazyVim plugin errors, updating plugins after breaking changes, or diagnosing colorscheme/startup issues.
Launch Neovim in a debugging workflow to reproduce the issue and collect error logs.
High-intent search queries and answers about installing and using this skill.
To troubleshoot Neovim startup failures after a LazyVim update, launch Neovim in a debugging workflow to reproduce the issue, collect error logs, identify the failing plugin, and apply an incremental fix.
Fixing LazyVim plugin errors from breaking changes involves diagnosing the specific plugin conflict and applying safe, incremental debugging steps to update or repair the affected plugins within your Neovim environment.
Diagnosing Neovim colorscheme issues requires accessing the Neovim binary and using incremental debugging steps to isolate the problematic colorscheme or plugin conflict causing the visual errors.
Yes, troubleshooting Neovim and LazyVim configuration problems requires an active developer environment using Neovim with LazyVim installed, along with access to the Neovim binary to execute debugging steps.
Neovim plugin conflicts occur during breaking updates or configuration errors; identify the failing plugin by reproducing the issue in a debugging workflow and reviewing the collected Neovim error logs.
SaschaLehConfigure Neovim environments with LazyVim conventions and Lua scripting.
matt-rileyValidate Neovim Lua configurations, plugin wiring, and startup behavior.
minusfiveGuide Neovim configuration management with LazyVim and Lua scripting.
trentshainesConfigure LazyVim plugins, keybindings, and Lua syntax in Neovim.
