agentleFS
Sign inStart free
ivyivy/dotfiles/.claude/skills/nvim/SKILL.md

nvim

Skill15 starsChanged 13 months agoISCView on GitHub

Use when troubleshooting Neovim/LazyVim plugin errors, updating plugins after breaking changes, or diagnosing colorscheme/startup issues.

  • Deletes or force-pushes

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check [ERROR] lines — these come from snacks.notifier history (where LazyVim routes errors)

    line 66
  2. Very specific:

    Clear compiled cache: if theme-related: rm -rf ~/.cache/catppuccin

    line 74
  3. Very specific:

    Run :Lazy update in Neovim (or headless equivalent)

    line 80
  4. Very specific:

    Never: use inline -c "lua ..." — shell escaping mangles quotes.

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Neovim/LazyVim Troubleshooting & Updates

Arguments

$ARGUMENTS

Reference

LazyVim is installed on this machine — read its source, not documentation about it:

WhatWhere
LazyVim itself~/.local/share/nvim/lazy/LazyVim/lua/lazyvim/ — config/, plugins/, util/
Default plugin specs.../lua/lazyvim/plugins/*.lua (coding, editor, ui, lsp/, extras/)
A plugin's own source~/.local/share/nvim/lazy/<plugin>/
Resolved versions~/.config/nvim/lazy-lock.json

Your overrides in lua/plugins/ merge against those default specs, so when a keymap or option appears from nowhere, grep lua/lazyvim/plugins/ to find what set it.

Key Paths

WhatSource (edit here)Installed (read-only)
Plugin specshome/dot_config/nvim/lua/plugins/~/.config/nvim/lua/plugins/
Lockfilehome/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.

  1. Copy debug script: cp .claude/skills/nvim/nvim-debug.lua /tmp/nvim-debug.lua
  2. Launch: tmux new-session -d -s nvim-debug -x 200 -y 50 "nvim -S /tmp/nvim-debug.lua"
  3. Wait + read: sleep 8 && cat /tmp/nvim-debug-output.txt
  4. Check [ERROR] lines — these come from snacks.notifier history (where LazyVim routes errors)

Mode: fix <plugin>

  1. Compare lockfiles — if installed differs from source, version drift caused the break
  2. Check plugin history: git -C ~/.local/share/nvim/lazy/<plugin> log --oneline --grep="refactor!\|BREAKING" --all
  3. Check upstream LazyVim: grep -rl "<plugin>" ~/.local/share/nvim/lazy/LazyVim/lua/lazyvim/ — they often fix breaking changes first
  4. Edit source in home/dot_config/nvim/lua/plugins/, then chezmoi diff and chezmoi apply
  5. Clear compiled cache if theme-related: rm -rf ~/.cache/catppuccin
  6. Re-run debug mode to verify
  7. Sync lockfile: cp ~/.config/nvim/lazy-lock.json home/dot_config/nvim/lazy-lock.json

Mode: update

  1. Run :Lazy update in Neovim (or headless equivalent)
  2. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free