nvim-context

星标13

分支0

更新时间2026年7月11日 07:57

Use when working on a project that has a running Neovim instance via vibing.nvim (the vibing-nvim MCP server is connected). Reads live buffer, window, cursor, and selection state through vibing-nvim MCP tools before editing or answering, instead of relying on stale file reads or guesses about what the user currently has open or selected.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

shabaraba

shabaraba/vibing.nvim

打开 GitHub 仓库查看创作者相关仓库

下载

Neovim Live Context

When the vibing-nvim MCP server is available, a real Neovim instance is running and its in-memory state (open buffers, splits, cursor position, unsaved edits) is the ground truth — it can differ from what's on disk. Prefer live state over assumptions whenever the user references "this file", "current buffer", "my selection", "what I have open", etc.

Workflow

Ground yourself first. Call mcp__vibing-nvim__nvim_get_info for the active file and mcp__vibing-nvim__nvim_list_windows / mcp__vibing-nvim__nvim_list_buffers to see everything open across splits/tabs before deciding which file the user means.
Use the real selection. If the user mentions a visual selection, call mcp__vibing-nvim__nvim_get_visual_selection instead of asking them to paste code.
Respect unsaved state. mcp__vibing-nvim__nvim_get_buffer returns the buffer's current content, which may include unsaved edits that differ from the file on disk — read the buffer, not the file, when a buffer for that path is already loaded.
Cursor-relative requests. For "here", "at my cursor", "this function" type requests, use mcp__vibing-nvim__nvim_get_cursor to resolve the exact line/column before acting.
Actual edits still go through your normal file tools (Read/Edit/Write). The vibing-nvim MCP tools are for observing and controlling the live editor (buffers, windows, commands), not a substitute for making code changes.

Graceful degradation

If vibing-nvim MCP calls fail or time out (no running Neovim instance, RPC not connected), don't retry repeatedly — but don't fail silently either:

Say so. Note briefly that live Neovim state isn't available, so you're working from on-disk file content, which may not match what the user actually has open (unsaved edits, a different selection, etc.).
Fall back to normal file-based tools (Read/Edit/Write) for the rest of the task.
Don't mix stale and live state. If vibing-nvim calls start succeeding again later in the same task (Neovim was started or reconnected), re-read the buffer via mcp__vibing-nvim__nvim_get_buffer before making further edits — don't keep acting on the on-disk snapshot from the degraded period.

同仓库更多 Skills

同仓库

vibing-worktree

shabaraba/vibing.nvim

Create, list, attach to, and finish git-worktree-backed isolated work areas for vibing.nvim chats, entirely via natural language — no separate UI. Use when the user wants to isolate work in its own worktree ("split this into its own worktree", "start this in isolation"), wants to see what worktrees/branches exist ("what worktrees do I have", "what's in progress"), wants to switch/attach the current or a new chat to an existing worktree ("let's go into the auth-fix worktree", "attach to worktree X"), or wants to clean one up when done ("clean up this worktree", "I'm done with this branch's worktree").

2026-07-1113

nvim-lsp-navigation

shabaraba/vibing.nvim

Use when navigating or analyzing a codebase that's open in a running Neovim instance via vibing.nvim with an LSP client attached. Prefers the vibing-nvim MCP LSP tools (definitions, references, hover, diagnostics, symbols, call hierarchy) over text search for "where is X defined/used/called", "what type is this", "what's broken here" style questions, since they reflect language-aware, live analysis rather than a text match.

2026-07-1113

vibing-chat-recall

shabaraba/vibing.nvim

Use when a vibing.nvim chat session's context feels lost or discontinuous — after a session reset, a dropped connection, or when Claude's own reasoning no longer matches what was discussed earlier in this conversation. Re-reads this conversation's own chat buffer (the file whose path is announced via the "Current vibing.nvim chat buffer file:" line in the system prompt) to silently restore context. Also invoke when the user explicitly asks to "remember", "recall", or "re-read the chat history" (in any language). Not for browsing other, unrelated past chat files — use vibing-chat-search for that.

2026-07-1013

vibing-chat-search

shabaraba/vibing.nvim

Use when the user wants to find a past vibing.nvim conversation by topic — phrases like "前に〜について聞いたことあったっけ", "did we talk about X before", "find that chat where I asked about Y". Searches every chat file under .vibing/chat/ (both User and Assistant content) for a natural-language query, narrows candidates with grep, then reads and semantically judges the survivors before presenting matches. Not for recovering this conversation's own lost context — use vibing-chat-recall for that.

2026-07-1013

test-design

shabaraba/vibing.nvim

Automatically design comprehensive E2E test cases for newly implemented vibing.nvim features. Use immediately after completing feature implementation (Phase 5.4) and before running E2E tests. Generates test scenarios covering Happy paths, Error cases, Edge cases, and Integration points with priority ranking (Critical/High/Medium/Low) and ready-to-use test code templates using e2e_helper.lua.

2026-01-3013

github-flow-for-claude-on-web

shabaraba/vibing.nvim

Complete GitHub workflow for Claude Code on the web. ALL GitHub operations MUST use REST API (never gh CLI). Includes branch naming (claude/*-sessionId), push retry logic, PR/issue management via API, and complete workflows. Use for all GitHub interactions in Claude Code web environment.

2025-12-2113

name	nvim-context
description	Use when working on a project that has a running Neovim instance via vibing.nvim (the vibing-nvim MCP server is connected). Reads live buffer, window, cursor, and selection state through vibing-nvim MCP tools before editing or answering, instead of relying on stale file reads or guesses about what the user currently has open or selected.
user-invocable	false

Neovim Live Context

Workflow

Ground yourself first. Call mcp__vibing-nvim__nvim_get_info for the active file and mcp__vibing-nvim__nvim_list_windows / mcp__vibing-nvim__nvim_list_buffers to see everything open across splits/tabs before deciding which file the user means.
Use the real selection. If the user mentions a visual selection, call mcp__vibing-nvim__nvim_get_visual_selection instead of asking them to paste code.
Respect unsaved state. mcp__vibing-nvim__nvim_get_buffer returns the buffer's current content, which may include unsaved edits that differ from the file on disk — read the buffer, not the file, when a buffer for that path is already loaded.
Cursor-relative requests. For "here", "at my cursor", "this function" type requests, use mcp__vibing-nvim__nvim_get_cursor to resolve the exact line/column before acting.
Actual edits still go through your normal file tools (Read/Edit/Write). The vibing-nvim MCP tools are for observing and controlling the live editor (buffers, windows, commands), not a substitute for making code changes.

Graceful degradation

If vibing-nvim MCP calls fail or time out (no running Neovim instance, RPC not connected), don't retry repeatedly — but don't fail silently either:

Say so. Note briefly that live Neovim state isn't available, so you're working from on-disk file content, which may not match what the user actually has open (unsaved edits, a different selection, etc.).
Fall back to normal file-based tools (Read/Edit/Write) for the rest of the task.
Don't mix stale and live state. If vibing-nvim calls start succeeding again later in the same task (Neovim was started or reconnected), re-read the buffer via mcp__vibing-nvim__nvim_get_buffer before making further edits — don't keep acting on the on-disk snapshot from the degraded period.