nvim-help

Answers Neovim usage questions by inspecting the user's actual configuration files.

Updated Jan 30, 2026

Search Tags:#lua #lazy.nvim #neovim #nvim #keybindings #plugin configuration #editor help

Ready to run

npx skills add https://github.com/RyoMa99/chezmoi_dotfiles --skill nvim-help-ryoma99

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nvim-help
Source: https://github.com/RyoMa99/chezmoi_dotfiles/tree/main/dot_claude/skills/nvim-help
Command: npx skills add https://github.com/RyoMa99/chezmoi_dotfiles --skill nvim-help-ryoma99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Generic Neovim advice often conflicts with a user's actual setup. This Skill answers Neovim questions by first reading the user's real configuration under ~/.config/nvim/, so keybindings, plugin behavior, and workflows match what is actually installed. ## Core Features & Use Cases - Config-grounded answers: Scans ~/.config/nvim/lua/plugins/ and related files before responding, so answers reflect installed plugins and custom keymaps. - Question-type routing: Maps question categories (keybindings, file operations, UI, LSP, search) to the specific config files that need inspection. - Use Case: A user asks "how do I search files?" and receives the exact Telescope keybindings defined in their own config rather than generic defaults. ## Quick Start Ask how to perform a specific action in Neovim, such as what keybinding opens the file explorer in my setup.

Frequently Asked Questions about nvim-help

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find my Neovim keybindings for a specific plugin?▼

Check the plugin's spec file under ~/.config/nvim/lua/plugins/, where the keys table defines its keybindings. Global keymaps live in init.lua or files under ~/.config/nvim/lua/. This Skill reads those files and reports the exact bindings in your setup.

How to answer Neovim questions based on my own config?▼

First list the files in ~/.config/nvim/lua/plugins/ to see installed plugins, then read the config files relevant to the question. Answers should cite your actual keybindings and settings rather than generic Neovim defaults.

Does this work with lazy.nvim plugin configurations?▼

Yes, it targets the common lazy.nvim layout where each plugin has a spec file in lua/plugins/ containing opts and keys. It reads those specs to determine installed plugins and their configured behavior.

Can this add or remove Neovim plugins for me?▼

No, plugin installation and removal are out of scope. When a question requires adding or deleting a plugin, the request is delegated to the separate nvim-plugin-management skill instead of modifying config files directly.

Why does it read my config before answering simple Vim questions?▼

Custom keymaps in init.lua can override default Vim behavior, so even general questions may have different answers in your environment. For purely standard Vim operations it only checks init.lua for conflicting mappings.