nixcf-nixvim

Maintains and reviews Nixvim and Home Manager Neovim configuration across NixOS host profiles.

Updated Jun 23, 2024
One-click install
npx skills add https://github.com/lifeich1/nixcf --skill nixcf-nixvim-lifeich1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nixcf-nixvim
Source: https://github.com/lifeich1/nixcf/tree/main/.agents/skills/nixcf-nixvim
Command: npx skills add https://github.com/lifeich1/nixcf --skill nixcf-nixvim-lifeich1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing a Nixvim-based Neovim configuration inside a multi-host NixOS flake is error-prone: plugin ownership, LSP executable packages, host-scoped conditions, and secret handling can easily drift or break. This Skill guides safe, scoped changes to the repository's Neovim setup across the GTR7, XPS13, and Raspberry Pi profiles. ## Core Features & Use Cases - Scoped change workflow: Establishes context from flake.nix and profile files, resolves ambiguous decisions before editing, and keeps Nixvim versus Home Manager ownership explicit. - Proportional validation: Runs source-safety gates, builds affected Nixvim wrappers per architecture, and executes headless Neovim smoke tests without launching an interactive UI. - Secret-safe editing: Enforces runtime-only loading of API keys and tokens so credentials never enter Nix expressions, generated init files, or the Nix store. - Use Case: Add a new LSP server to the shared Neovim config, verify its executable package ownership, build both desktop wrappers, and confirm the Pi profile stays LSP-disabled. ## Quick Start Use the nixcf-nixvim skill to add a Treesitter grammar and LSP server to the shared Neovim configuration and validate the affected host wrappers.

Frequently Asked Questions about nixcf-nixvim

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

FAQPage Schema
How do I add an LSP server to a Nixvim configuration?▼

Add the server under the shared fool.nvim.lsp condition, assign exactly one package owner for its executable, and verify the installed package provides the launched command. Then build each affected host's Nixvim wrapper and run a headless smoke test.

How do I change Neovim plugins in a NixOS Home Manager flake?▼

Prefer a typed Nixvim module over extraPlugins with raw setup, keeping installation and setup under one obvious enable condition. Place wrapper settings in fool/nvim/default.nix and validate by building the wrapper without launching Neovim.

Can Nixvim configuration differ between hosts like a Raspberry Pi?▼

Yes, host-scoped options gate behavior per profile, and the Pi profile remains LSP-disabled unless explicitly changed. Treat the Pi as aarch64-linux and never assume an x86_64-linux package output exists there.

How do I handle API keys in a Nixvim AI plugin setup?▼

Load API keys and tokens only at runtime through an environment variable or protected runtime file. Never place secret values in Nix expressions, generated init files, Git-tracked files, or Nix store paths.

Why does a Nixvim change need a source-safety check before building?▼

The check-nix-source-safety.sh gate prevents Nix evaluation from reading secret-containing sources before any repo-consuming command runs. If it blocks, report the path and category output instead of bypassing it with a narrower attribute.