nvim-config

Edit Neovim Lua configurations and diagnose plugin behavior in local setups.

3|Updated Mar 7, 2020
One-click install
npx skills add https://github.com/qsdrqs/dotfiles --skill nvim-config-qsdrqs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nvim-config
Source: https://github.com/qsdrqs/dotfiles/tree/main/opencode/skills/nvim-config
Command: npx skills add https://github.com/qsdrqs/dotfiles --skill nvim-config-qsdrqs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes Neovim configuration work within this dotfiles repo, easing tasks like editing configs, tuning plugins, and troubleshooting issues.

Core Features & Use Cases

  • Facilitates a code-first workflow: read local config and plugin source, then validate changes before applying.
  • Guides workflow for editing nvim config, keymaps, LSP/formatters, UI tweaks, and performance improvements.
  • Use Case: When you need to adjust a plugin's behavior or diagnose startup slowdowns in Neovim.

Quick Start

Review the local Neovim configuration in this repo and propose minimal, safe edits that align with the existing structure.

Frequently Asked Questions about nvim-config

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

FAQPage Schema
How do I edit Neovim Lua config files to adjust plugin behavior?

To debug Neovim LSP and formatter configurations, read local plugin sources and validate current settings against up-to-date API docs. Apply minimal edits to Lua config files to resolve formatter integration issues and ensure proper LSP server attachments.

What is the best way to diagnose Neovim startup slowdowns in a dotfiles repo?

Diagnosing Neovim startup slowdowns requires reading local code and plugin sources to identify performance bottlenecks. Analyze plugin loading behavior and apply minimal Lua configuration edits to optimize startup time within the existing dotfiles structure.

Can I update keymaps and UI tweaks without breaking my Neovim setup?

You can update keymaps and UI tweaks safely by reviewing the local Neovim configuration first. Propose minimal, safe edits that align with the existing Lua structure to ensure UI changes integrate without breaking current plugin behavior.

Does managing Neovim config require checking API docs before applying changes?

Managing Neovim config requires consulting up-to-date API docs before applying changes. This code-first workflow validates proposed plugin spec modifications and keymap adjustments against current Neovim Lua APIs to prevent configuration errors.

Why are my Neovim plugin specs not loading correctly after a config edit?

Neovim plugin specs may fail to load correctly after a config edit if changes are not aligned with the existing repository structure. Reading local plugin source code helps identify mismatched dependencies or invalid Lua syntax causing loading failures.