base.nvim

Create conventional commits for Neovim plugins that are compatible with release-please and follow SemVer. Use when the user asks to commit changes, make a git commit, or says "/commit" while working in a Neovim plugin project. Analyzes the diff to produce correctly scoped, typed commit messages that release-please can parse into changelog entries and semantic version bumps. Also use when the user asks about commit message format for their Neovim plugin or wants to know what type a change should be.

Write, update, and improve Neovim plugin help documentation (vimdoc) in doc/<plugin>.txt. Use when the user asks to write docs, update docs, generate the help file, add documentation for a function, or mentions vimdoc, help tags, or plugin documentation. Reads the plugin source code to extract API, commands, configuration, and other info from LuaCATS annotations and code structure, then writes a properly formatted doc/<plugin>.txt following vimdoc conventions. Do not use for general Neovim :help lookups (use nvim-help skill instead) or for writing README.md, CHANGELOG.md, or other non-vimdoc documentation.

Search and read Neovim's built-in :help documentation to look up API signatures, parameter types, option values, and event specifications from the user's installed runtime. Use when the user wants to consult reference material — function docs, help tags, option descriptions — not when they want to write, create, or debug something. For writing Neovim Lua code, composing Treesitter queries, or fixing config issues, use general coding tools instead. Pairs with Context7 (neovim/neovim) for code examples; this skill provides exact local signatures and docs.

Initialize a Neovim plugin project after cloning from base.nvim template. Run once at the start of development to verify the development environment is set up correctly. Use when the user says "init", "setup", "initialize", "check environment", "nvim-init", or asks to verify their Neovim plugin development setup. Also use when the user says they just cloned the template or wants to start developing a Neovim plugin. Do not use for general Neovim plugin development tasks (use nvim-plugin) or for running tests (use nvim-test).

Neovim plugin development best practices and patterns. Use when planning, editing, implementing, or reviewing Neovim Lua plugin code — structuring a new plugin, writing setup/config, highlights, autocmds, keymaps, health checks, type annotations, debounce, state management, or user commands. Also use when the user asks about plugin architecture, conventions, or "how should I implement" a Neovim plugin feature. Do not use for general Lua development unrelated to Neovim plugins, Neovim configuration (init.lua), or running/debugging tests (use nvim-test).

Execute tests and diagnose failures for this Neovim plugin. Use when the user says "run tests", "run the suite", or asks to execute the test suite (full, single file, or offline). Also use when the user pastes test error output, asks what a test failure means, or needs help fixing a broken test. The test stack is mini.test + luassert with _spec.lua files. Do not trigger for writing tests, learning test APIs, setting up testing from scratch, or non-Neovim tools.