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.
Fetches live Neovim context (cursor position, file, selection, diagnostics) to answer questions about "this line", "current file", or "selection" in the user's editor.
/plugin marketplace add majjoha/nvim-context/plugin install nvim-context@nvim-contextThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Provides live context from the user's Neovim editor session to help answer context-aware questions about code.
nvim-context tool to get the current editor state.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": []
}
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.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.