nvim-context
Get the current Neovim context as JSON (cursor position, current file, visual selection and diagnostics) to help answer questions about code at the current cursor position, visual selections and diagnostics. Use when users ask about "this line", "current file", "selection" or need context about their Neovim editor state.
When & Why to Use This Skill
This Claude skill provides seamless integration with the Neovim editor, allowing the AI to access real-time context such as cursor position, active file paths, visual selections, and LSP diagnostics. It enhances the developer experience by enabling context-aware code analysis, instant debugging, and precise explanations without the need for manual copy-pasting, making AI-assisted coding more fluid and accurate.
Use Cases
- Instant Debugging: Analyze live LSP diagnostics and error messages at the current cursor position to identify and resolve bugs immediately.
- Code Explanation: Provide detailed breakdowns and logic explanations for specific code segments highlighted via Neovim's visual selection.
- Contextual Navigation: Help developers understand their current location within a project by retrieving file paths and line numbers during complex refactoring.
- Interactive Code Review: Use the 'current file' context to perform on-the-fly reviews and suggest improvements based on the active editor state.
| name | nvim-context |
|---|---|
| description | > |
Neovim context provider
Purpose
Provides live context from the user's Neovim editor session to help answer context-aware questions about code.
How it works
- Executes the
nvim-contexttool to get the current editor state. - Returns JSON data including cursor position, open file, visual selection and diagnostics.
- Use this information to understand references like "this line", "the selection", "current file", etc.
Usage examples
- "What's wrong with this line?" → Check diagnostics at cursor
- "Explain the selected code" → Analyze visual selection
- "What file am I in?" → Return current file path
- "Show me all errors" → List all LSP diagnostics
Technical details
To use this skill, execute the nvim-context CLI command which outputs JSON:
{
"cursor": {
"line": 43,
"col": 3
},
"file": "/path/to/current/file.rb",
"selection": null,
"diagnostics": []
}
Implementation
When this skill is loaded, execute nvim-context via Bash and parse the JSON
output to understand the current editor state. Use the returned data to answer
user questions about their code.