nvim-lazy-mini-setup

Bootstrap and migrate modular Neovim configurations using lazy.nvim and mini.nvim.

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tarabakz25/my-skills --skill nvim-lazy-mini-setup-tarabakz25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nvim-lazy-mini-setup
Source: https://github.com/tarabakz25/my-skills/tree/main/nvim-lazy-mini-setup
Command: npx skills add https://github.com/tarabakz25/my-skills --skill nvim-lazy-mini-setup-tarabakz25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up or restructuring a Neovim configuration is error-prone: plugin manager bootstrapping, lockfile handling, and module organization often cause startup failures and inconsistent setups. This Skill guides the creation, migration, and maintenance of a clean modular Neovim config built on lazy.nvim and mini.nvim. ## Core Features & Use Cases - Config Bootstrapping: Generates a modular init.lua with lazy.nvim bootstrap, lua/options, and lua/plugins structure. - mini.nvim Configuration: Provides recipes and sensible defaults for mini.files, mini.surround, mini.comment, mini.statusline, mini.starter, mini.pick, and more. - Migration Support: Includes a checklist for converting packadd or mini.deps based configs to lazy.nvim with lockfile regeneration. - Use Case: You have an existing Neovim config using mini.deps and want to switch to lazy.nvim with one plugin spec file per feature, then verify with :Lazy sync and :checkhealth. ## Quick Start Ask the agent to set up a new Neovim config using lazy.nvim and mini.nvim with mini.files, mini.surround, and mini.statusline enabled.

Frequently Asked Questions about nvim-lazy-mini-setup

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

FAQPage Schema
How do I set up Neovim with lazy.nvim and mini.nvim?▼

Create an init.lua that clones lazy.nvim into stdpath('data')/lazy/lazy.nvim, prepends it to runtimepath, then calls require('lazy').setup with plugin specs. Add echasnovski/mini.nvim as a spec and call setup() for each mini module you want.

How to migrate from mini.deps to lazy.nvim?▼

Add the lazy.nvim bootstrap to init.lua, translate each plugin into a lazy spec under lua/plugins/, then remove mini.deps registration calls. Run :Lazy sync to regenerate lazy-lock.json and verify with :checkhealth after restarting.

Which mini.nvim modules should I enable first?▼

Common starting modules are mini.files for file exploration, mini.surround for surround motions, mini.comment for commenting, and mini.statusline for a lightweight statusline. Enable only what you need, since mini.basics can conflict with existing option tuning.

Can I use lazy.nvim together with mini.deps?▼

Mixing plugin managers is possible but discouraged because it complicates lockfile and loading behavior. The recommended approach is to pick lazy.nvim as the single manager and migrate all mini.deps registrations into lazy specs.

Why does lazy.nvim fail to bootstrap on first launch?▼

Bootstrap failures usually come from git not being available, network issues cloning the repository, or the runtimepath prepend happening after require('lazy'). Ensure the clone targets stdpath('data')/lazy/lazy.nvim and rtp is prepended before setup.