nvsinner-change-control

Classify NvSinner repository changes and apply project-specific modification constraints.

1|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/anderssonq/nvsinner --skill nvsinner-change-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nvsinner-change-control
Source: https://github.com/anderssonq/nvsinner/tree/main/.claude/skills/nvsinner-change-control
Command: npx skills add https://github.com/anderssonq/nvsinner --skill nvsinner-change-control

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unsafe or inconsistent changes to the NvSinner Neovim distribution by enforcing change classification, ownership rules, project invariants, and validation requirements before modifications are considered complete.

Core Features & Use Cases

  • Change Classification: Guides contributors in routing plugin specs, core modules, distro scripts, and documentation changes through the correct review constraints.
  • Safety Guardrails: Preserves critical architecture rules around lazy.nvim loading, palette ownership, LSP configuration, terminal session management, and update workflows.
  • Validation Workflow: Defines required syntax checks, boot verification, tests, plugin checks, and documentation synchronization steps for repository changes.

Quick Start

Load the nvsinner-change-control skill before editing any NvSinner files to classify the change and follow the required validation gates.

Frequently Asked Questions about nvsinner-change-control

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

FAQPage Schema
How do I safely update plugins and core Lua modules in a Neovim distribution?

Safe Neovim plugin updates require classifying changes and applying architectural invariants, ownership rules, and validation commands. The workflow enforces syntax checks, boot verification, and documentation synchronization before modifications are considered complete.

What are lazy.nvim loading constraints when modifying Neovim plugin specs?

lazy.nvim loading constraints preserve critical architecture rules around palette ownership, LSP configuration, and terminal session management. Change control enforces these invariants to prevent breaking the Neovim distribution's lazy loading behavior during plugin spec modifications.

What validation steps are required before merging changes to a Neovim configuration?

Pre-merge verification for Neovim configurations requires running syntax checks, boot verification, tests, and plugin checks. The workflow mandates these validation gates alongside documentation synchronization to ensure repository modifications are complete and safe.

Can I modify distro scripts and keymaps without following change classification rules?

No, distro scripts and keymaps must route through correct review constraints based on change classification. The safety guardrails enforce ownership rules and architectural invariants across all NvSinner modifications, including UI changes and documentation updates.

Why does my Neovim distribution break after updating core Lua modules?

Neovim distributions break when core Lua module updates violate architectural invariants or skip validation workflows. Enforcing change classification, syntax checks, and boot verification before modifications are complete prevents unsafe or inconsistent codebase changes.