naming-convention

Enforce nixpkgs naming conventions for files, variables, and packages.

3|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/ncaq/konoka --skill naming-convention-ncaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming-convention
Source: https://github.com/ncaq/konoka/tree/main/plugins/nix-tasuke/skills/naming-convention
Command: npx skills add https://github.com/ncaq/konoka --skill naming-convention-ncaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nix projects often suffer from inconsistent naming across files, variables, packages, and NixOS options. This skill codifies official nixpkgs naming standards to help teams write more readable, maintainable Nix code.

Core Features & Use Cases

  • Enforces file and directory naming using kebab-case (e.g., all-packages.nix).
  • Guides variable and attribute naming rules (lowerCamelCase for simple identifiers, kebab-case for packages and derivations).
  • Helps code reviews and onboarding by providing a reference for Nix naming conventions when writing or reviewing Nix code.

Quick Start

Ask me to verify a Nix file against official nixpkgs naming conventions and provide a corrected version.

Frequently Asked Questions about naming-convention

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

FAQPage Schema
What are the official nixpkgs naming conventions for variables and packages?

Official nixpkgs naming conventions require lowerCamelCase for simple variable identifiers and kebab-case for packages and derivations. This standardization ensures your Nix codebase remains readable and maintainable across development workflows.

How do I check my Nix file against nixpkgs coding standards?

You can verify a Nix file against nixpkgs coding standards by checking file and directory naming using kebab-case, such as all-packages.nix. Apply the rules to your codebase to identify inconsistencies and generate a corrected version.

When should I use kebab-case vs lowerCamelCase in NixOS modules?

Use kebab-case for file names, directory structures, packages, and NixOS options, while lowerCamelCase is reserved for simple variable identifiers. Special files like default.nix and flake.nix must follow these exact casing rules.

Does nixpkgs have a standard naming format for boolean enable flags?

Yes, nixpkgs coding standards include specific naming rules for boolean enable flags. Enforcing these naming conventions across your Nix code helps maintain consistency for NixOS options and module attributes during code reviews.

What is the best way to enforce Nix naming rules in code reviews?

The best way to enforce Nix naming rules is by referencing codified official nixpkgs standards during reviews. Check variables, files, and packages against kebab-case and lowerCamelCase rules to streamline onboarding and improve code readability.