ivy/nvim
.claude/skills/nvim/SKILL.md
Use when troubleshooting Neovim/LazyVim plugin errors, updating plugins after breaking changes, or diagnosing colorscheme/startup issues.
$ install --global
skillsauthnpx skillsauth add ivy/dotfiles nvimInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 11:00 AM17.2s1 file scanned
SKILL.md
- name:
- nvim
- description:
- Use when troubleshooting Neovim/LazyVim plugin errors, updating plugins after breaking changes, or diagnosing colorscheme/startup issues.
- argument-hint:
- [debug | update | fix <plugin>]
- context:
- default
- - Bash(nvim --version:
- *)
- - Bash(nvim --headless:
- *)
- - Bash(tmux new-session -d -s nvim-debug:
- *)
- - Bash(tmux kill-session -t nvim-debug:
- *)
- - Bash(tmux capture-pane -t nvim-debug:
- *)
- - Bash(ls:
- *)
- - Bash(cat /tmp/nvim-debug*:
- *)
- - Bash(git -C ~/.local/share/nvim/lazy:
- *)
- - Bash(chezmoi diff:
- *)
- - Bash(chezmoi status:
- *)
- - Bash(sleep:
- *)
Neovim/LazyVim Troubleshooting & Updates
Arguments
$ARGUMENTS
Reference
LazyVim docs: docs/reference/lazyvim-github-io.txt. If missing, run /gitingest https://github.com/LazyVim/lazyvim.github.io docs/**.md first.
Key Paths
| What | Source (edit here) | Installed (read-only) |
|------|-------------------|----------------------|
| Plugin specs | home/dot_config/nvim/lua/plugins/ | ~/.config/nvim/lua/plugins/ |
| Lockfile | home/dot_config/nvim/lazy-lock.json | ~/.config/nvim/lazy-lock.json |
| Installed plugins | — | ~/.local/share/nvim/lazy/<plugin>/ |
Always edit source (home/dot_config/nvim/), never destination. Deploy with chezmoi apply.
Mode: debug (default)
Use tmux, not headless — --headless skips lazy-loaded UI plugins (bufferline, noice, lualine), hiding real errors.
- Copy debug script:
cp .claude/skills/nvim/nvim-debug.lua /tmp/nvim-debug.lua - Launch:
tmux new-session -d -s nvim-debug -x 200 -y 50 "nvim -S /tmp/nvim-debug.lua" - Wait + read:
sleep 8 && cat /tmp/nvim-debug-output.txt - Check
[ERROR]lines — these come fromsnacks.notifierhistory (where LazyVim routes errors)
Mode: fix <plugin>
- Compare lockfiles — if installed differs from source, version drift caused the break
- Check plugin history:
git -C ~/.local/share/nvim/lazy/<plugin> log --oneline --grep="refactor!\|BREAKING" --all - Check upstream LazyVim:
grep -rl "<plugin>" ~/.local/share/nvim/lazy/LazyVim/lua/lazyvim/— they often fix breaking changes first - Edit source in
home/dot_config/nvim/lua/plugins/, thenchezmoi diffandchezmoi apply - Clear compiled cache if theme-related:
rm -rf ~/.cache/catppuccin - Re-run debug mode to verify
- Sync lockfile:
cp ~/.config/nvim/lazy-lock.json home/dot_config/nvim/lazy-lock.json
Mode: update
- Run
:Lazy updatein Neovim (or headless equivalent) - Debug mode → fix any breakage → sync lockfile back to source
Anti-patterns
- Never use inline
-c "lua ..."— shell escaping mangles quotes. Write temp Lua files. - Never edit
~/.config/nvim/directly — chezmoi owns the destination. - Never ignore lockfile drift — sync installed back to source or breakage recurs.
Examples
/nvim → Run debug, report errors
/nvim fix catppuccin → Fix catppuccin after breaking update
/nvim update → Update all plugins, fix breakage
Related Skills
ivy/handoff
tools
VerifiedTrustedCommunity
Write a handoff brief summarizing the current conversation so a fresh agent can pick up the work. Writes to a file if given, otherwise copies to the clipboard.
7SKILL.mdUpdated Jun 4, 2026
ivy/mob
data-ai
VerifiedTrustedCommunity
Use when the user wants to set, change, or clear git commit co-authors for pair or mob programming.
7SKILL.mdUpdated Apr 16, 2026
ivy/hk
tools
VerifiedTrustedCommunity
Use when bootstrapping hk pre-commit hooks for a project.
7SKILL.mdUpdated Apr 16, 2026
ivy/grill-me
testing
VerifiedTrustedCommunity
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
7SKILL.mdUpdated Apr 16, 2026