菜单
Neovim configuration help - plugins, LSP setup, troubleshooting. Use when asked about nvim, vim, editor config, or plugins. Trigger on: lazy.nvim, mason, LSP server, init.lua, kickstart, lspconfig, checkhealth, MasonCleanup.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | nvim |
| description | Neovim configuration help - plugins, LSP setup, troubleshooting. Use when asked about nvim, vim, editor config, or plugins. Trigger on: lazy.nvim, mason, LSP server, init.lua, kickstart, lspconfig, checkhealth, MasonCleanup. |
| user_invocable | false |
~/.config/nvim/init.lua (symlinked from ~/.dotfiles/configs/base/nvim/.config/nvim/)
Read ~/.config/nvim/init.lua and extract plugins from the lazy.setup() call. Do not rely on a static list — the file is the source of truth.
LSP servers are managed in two ways:
| Type | Install Via | Examples | When to Use |
|---|---|---|---|
| Mason | ensure_installed | lua_ls, ts_ls, pyright | Standalone or runtime-agnostic servers |
| Project-local | vim.lsp.config | ruby_lsp | Servers that need project's runtime/deps |
Defined in mason_ensure list in init.lua. These install once and work everywhere.
Configured via vim.lsp.config() + vim.lsp.enable(). Run through bundler/venv to use project's versions.
Example for Ruby (requires gem 'ruby-lsp' in Gemfile):
vim.lsp.config('ruby_lsp', {
cmd = { 'bundle', 'exec', 'ruby-lsp' },
root_markers = { 'Gemfile', '.git' },
})
vim.lsp.enable('ruby_lsp')
mason_ensure (Mason name) and ensure_installed (lspconfig name)vim.lsp.config() + vim.lsp.enable() blockRun :MasonCleanup to remove Mason packages not in the mason_ensure list.
:Lazy:LspInfo, check :Mason for servers:checkhealth in nvimUse when planning non-trivial tasks, composing outputs, or managing knowledge work projects. Lifecycle toolkit with folio.yml-driven source-to-target composition and diverge-converge planning. Trigger on: design doc, spike, retro, wrap-up, observations, handoff, brief, gather, publish, burndown, work tracks.
Use when reviewing any SKILL.md, CLAUDE.md, reference file, or agentic documentation for quality — structure, description, progressive disclosure, writing style. Also use when validating tool conventions, checking contract compliance, or debugging lint failures in dotfiles CLI tools. Triggers: 'review my skill', 'check this skill', 'review this doc', 'is this SKILL.md good', 'skill quality', 'dendrik', 'lint', 'convention check'.
Use when managing Jira tickets, creating/editing issues, pushing descriptions and titles, searching with JQL, managing ticket lifecycle (parking, repurposing), or when needing Jira conventions, project field defaults, and content gotchas.
Manage and develop dotfiles — installation, updates, adding configs, troubleshooting symlinks, and repo development guidelines. Use when asked about dotfiles, system config, shell setup, or when making changes to the dotfiles repo. Trigger on: dot sync, dot health, dot validate, managed files, drift, private overlay, Brewfile, build artifacts, symlink map, dot fix, dot clean.
Conventional commit format, message conventions, green commit rules, and VCS history structuring for both git and jj (Jujutsu). Use when creating commits, amending commits, writing commit messages, describing jj changes (jj describe, jj new, jj split, jj squash), fixup commits, interactive rebase, stacked branch propagation, or deciding how to decompose work into commits. Applies to all repositories — always use this skill instead of Claude Code's default commit behavior.
A skill with broken markdown links.