neovim-advisor

Validate the user's Neovim configuration following modern best practices.

Interactive LSP (Language Server Protocol) configuration for specific languages with proper Mason, nvim-lspconfig, and nvim-cmp integration.

Profile Neovim startup time, identify bottlenecks, and provide actionable optimization recommendations.

Provide personalized Neovim plugin recommendations based on user workflow or by analyzing existing configuration.

Use this agent when the user needs to validate their Neovim configuration for best practices, structural issues, plugin syntax, or common mistakes. Examples: <example> Context: User has just modified their Neovim configuration and wants to ensure it follows best practices user: "I just updated my init.lua, can you check if everything looks good?" assistant: "I'll validate your Neovim configuration to check for best practices, structural issues, and common mistakes." <commentary> The user is asking for validation of their configuration after making changes. This is a perfect scenario for the config-validator agent which specializes in comprehensive Neovim config analysis. </commentary> </example> <example> Context: User explicitly asks for configuration validation user: "Is my Neovim config following best practices?" assistant: "I'll use the config-validator agent to analyze your Neovim configuration for best practices compliance." <commentary> Direct request for best practices validation. The config-validator agent will check structure, plugin syntax, organization, and common pitfalls. </commentary> </example> <example> Context: During conversation about Neovim plugins, assistant notices potential configuration issues user: "My telescope plugin isn't loading properly" assistant: "Let me validate your configuration to identify potential issues with the telescope setup." <commentary> Proactive triggering - the assistant recognizes that a plugin loading issue likely stems from configuration problems. The config-validator can identify syntax errors, dependency issues, or improper plugin specifications. </commentary> </example> <example> Context: User asks to check configuration after installing new plugins user: "I added a few new plugins, want to make sure I didn't break anything" assistant: "I'll run a comprehensive validation of your Neovim configuration to check for issues with the new plugins." <commentary> After adding plugins, it's critical to validate syntax, dependencies, and proper lazy.nvim specifications. The config-validator ensures the configuration remains valid and follows best practices. </commentary> </example>

Use this agent when users report slow Neovim startup times, ask about performance optimization, or need deep profiling of their configuration. Examples: <example>Context: User mentions their Neovim takes too long to start up. user: "My Neovim feels really slow lately, especially on startup. It takes like 3-4 seconds to open." assistant: "I'll use the performance-analyzer agent to run comprehensive profiling and identify what's causing the slow startup." <commentary>The user is experiencing slow startup times, which is a clear performance issue requiring deep analysis with startuptime profiling and bottleneck identification.</commentary></example><example>Context: User wants to optimize their configuration after adding several plugins. user: "I just installed about 15 new plugins. How can I tell if they're slowing things down?" assistant: "Let me analyze your Neovim performance to see the impact of those plugins." <commentary>The user wants to understand performance impact after configuration changes. The agent should baseline current performance and identify which plugins are heavy.</commentary></example><example>Context: User asks about lazy-loading optimization. user: "What's the best way to lazy-load my plugins? I heard it helps with startup time." assistant: "I'll profile your current setup and provide specific lazy-loading recommendations." <commentary>The user is asking about a specific optimization strategy. The agent should analyze current plugin loading patterns and suggest improvements.</commentary></example><example>Context: During conversation, startup time data shows abnormal values. user: "Can you help me set up Telescope?" assistant: "I notice from recent logs that your startup time might be higher than optimal. Before we proceed, would you like me to use the performance-analyzer agent to check for any performance issues?" <commentary>Proactive triggering when performance issues are detected during regular conversation, offering to investigate before continuing with the original task.</commentary></example>

Use this agent when analyzing Neovim plugins, suggesting improvements, checking for updates, recommending alternatives, or identifying unused plugins. Examples: <example>Context: User is discussing their Neovim setup and mentions slow startup times. user: "My Neovim takes forever to start, I have like 80 plugins installed" assistant: "I'll use the plugin-advisor agent to analyze your installed plugins, identify any that might be slowing startup, and suggest optimizations or alternatives." <commentary>Agent should trigger proactively because the user has a plugin-related performance issue that requires analysis of their installed plugins.</commentary></example> <example>Context: User wants to improve their development workflow. user: "What are the best plugins for TypeScript development these days?" assistant: "I'll use the plugin-advisor agent to provide current recommendations for TypeScript development, checking for modern alternatives and well-maintained plugins." <commentary>Agent should trigger because user is explicitly asking for plugin recommendations for a specific use case.</commentary></example> <example>Context: User is reviewing their configuration. user: "Is nvim-tree still the recommended file explorer or should I switch?" assistant: "I'll use the plugin-advisor agent to compare nvim-tree with modern alternatives like oil.nvim and neo-tree, checking maintenance status and community preferences." <commentary>Agent should trigger because user is asking about plugin alternatives and wants comparison of options.</commentary></example> <example>Context: During a conversation about workflow optimization. user: "I feel like I'm missing some essential plugins" assistant: "I'll use the plugin-advisor agent to analyze your current setup and identify any gaps in essential categories like debugging, testing, or Git integration." <commentary>Agent should trigger proactively to provide personalized plugin gap analysis based on user's existing configuration.</commentary></example>

Profiles Neovim startup performance and optimizes lazy.nvim plugin loading with targeted lazy-loading specs, priorities, and event triggers. Contains profiling workflow and bottleneck checklists. Make sure to use this skill whenever the user mentions slow neovim startup, neovim takes time to load, plugin profiling, lazy-loading, lazy.nvim config, startup time optimization, or neovim performance — even if the user doesn't say "lazy.nvim" explicitly.

Configures Neovim with the user's opinionated Lua patterns, namespaced config structure, LSP via Mason + nvim-lspconfig, and leader key conventions. Contains user-specific decisions and checklists Claude cannot know without this skill. Make sure to use this skill whenever the user mentions neovim, nvim, init.lua, LSP setup, keymaps, autocommands, neovim plugins, Mason, TypeScript LSP, slow LSP, neovim config, or any neovim question — even if Claude thinks it can answer from general knowledge.