vibing-nvim

Plugin vibing-nvim from marketplace vibing in shabaraba/vibing.nvim. Commands read from the repo's manifest — 3 days ago.

Skills (12)

• nvim-context

  Use only when the user's request depends on live Neovim state, such as the current buffer, cursor, visual selection, unsaved edits, windows, tabs, or an explicit request to use nvim tools. Do not use for ordinary questions or tasks that do not reference the active editor.

• nvim-lsp-navigation

  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

• vibing-chat-recall

  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 buffer announced via the "Curre

• vibing-chat-search

  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 cand

• vibing-code-tour

  Walk the user through a real execution path by opening the actual files and jumping to the actual lines in their running Neovim, instead of describing the path in chat text. Use when someone asks to be walked through how something works ("walk me through the auth flow", "give me a tour of how a requ

• vibing-orchestrate

  Run several independent tasks in parallel by creating worker vibing.nvim chats, handing each one a self-contained brief, and aggregating their results. Use when the user asks for parallel work ("do these three in parallel", "split this across separate chats", "並行でやって", "この2つを別々のチャットで").

• vibing-worker

  Use when this chat's system prompt states it was started by another vibing.nvim chat (an orchestrator). Covers where and when to report back, the report's shape, and what not to do — the full version of the protocol summarized in that system-prompt line.

• vibing-worktree-attach

  Attach the current or a new vibing.nvim chat to an already-existing git worktree via natural language — no separate UI. Use when the user wants to switch/attach a chat to an existing worktree ("let's go into the auth-fix worktree", "attach to worktree X", "continue in the feature-y worktree").

• vibing-worktree-create

  Create a new git-worktree-backed isolated work area for the current vibing.nvim chat 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", "give this its own branch").

• vibing-worktree-finish

  Remove a git-worktree-backed isolated work area for vibing.nvim chats via natural language — no separate UI. Use when the user wants to clean one up when done ("clean up this worktree", "I'm done with this branch's worktree", "remove the auth-fix worktree").

• vibing-worktree-list

  List git-worktree-backed isolated work areas for vibing.nvim chats via natural language — no separate UI. Use when the user wants to see what worktrees/branches exist ("what worktrees do I have", "what's in progress", "show me all worktrees").

• vibing-worktree-run

  Get a git worktree branch's code actually running (dev server, tests, CLI invocation, etc.) without merging or rebasing it, for vibing.nvim chats. Use when the user wants to run or try out a worktree branch for real ("I want to check this branch really works", "let me try this worktree's code for re

Subagents (1)

• nvim-navigator

  Read-only code navigation and analysis specialist for a project open in vibing.nvim. Use for "where is X defined/used", "what calls this function", "what's the type of this", or "what diagnostics exist here" questions — it answers using the live Neovim buffer/LSP state via vibing-nvim MCP tools inst

MCP servers (1)

• vibing-nvim

  runs: sh ${CLAUDE_PLUGIN_ROOT}/mcp-server/bin/run.sh

Similar plugins