nvim-config-review

Reviews Neovim configurations for deprecated APIs, version compatibility, performance, and layout without modifying files.

Updated Jul 4, 2023
One-click install
npx skills add https://github.com/kohdice/dotfiles --skill nvim-config-review-kohdice
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nvim-config-review
Source: https://github.com/kohdice/dotfiles/tree/main/config/agents/skills/nvim-config-review
Command: npx skills add https://github.com/kohdice/dotfiles --skill nvim-config-review-kohdice

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Neovim configurations silently accumulate deprecated API calls, archived plugins, and startup bottlenecks as the editor evolves across releases. This Skill audits a config against version-matched official documentation and reports findings with evidence, without editing any files or launching Neovim. ## Core Features & Use Cases - Version-anchored audit: Resolves the target Neovim version from user request, repository pins (Nix flake, .tool-versions), or the installed binary, then gates every finding on that version. - Four review lenses: Checks modern API adoption (vim.lsp.config, vim.pack), deprecated/removed APIs with grep patterns, startup and runtime performance, and runtimepath directory architecture. - Verified, sourced findings: Every finding includes path:line, offending code, the official replacement, and a source (:h tag or URL), grouped by High/Medium/Low severity. - Use Case: After upgrading to Neovim 0.12, run this Skill on your dotfiles repo to find calls like vim.diagnostic.goto_next() or the removed vim.diff(), plus archived plugins such as packer.nvim, and get a migration report. ## Quick Start Ask the AI to review the Neovim configuration in this repository for deprecated APIs and compatibility with the installed Neovim version.

Frequently Asked Questions about nvim-config-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my Neovim config for deprecated APIs?▼

Run this Skill against your config directory; it greps for deprecated patterns like vim.loop, get_active_clients, and nvim_buf_get_option, then confirms each hit in context. Findings are gated on your resolved target version so nothing is flagged before its deprecation applies.

How to migrate a Neovim config to 0.12?▼

The review identifies APIs removed in 0.12 such as vim.diff() and sign_define()-based diagnostic signs, plus 0.12 deprecations like the keymap buffer option. Each finding includes the official replacement and source documentation for the migration.

Does the review modify or test my Neovim configuration?▼

No, the Skill is strictly read-only: it never edits files, mutates git state, or launches Neovim to test loading. The only permitted command is nvim --version for target resolution; all findings come from reading code against official docs.

How is the target Neovim version determined?▼

An explicit user request wins first, then a repository pin such as a Nix flake or .tool-versions, then the installed binary via nvim --version. If none resolve, the review continues with version-independent checks and marks version-dependent advice as conditional.

What are the limitations of this Neovim config review?▼

The reference catalog covers up to Neovim 0.12.3; newer targets require checking official release notes, and unverifiable claims are labeled rather than reported as confirmed. It also does not measure actual startup time, since launching Neovim is outside its read-only contract.