nix-check

Check and validate NixOS configuration. Use when asked to check, validate, lint, or verify the nix config, flake, or configuration files.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

The Nix Configuration Checker is a specialized Claude skill designed to automate the validation, linting, and verification of NixOS configurations and flakes. It ensures code quality and system stability by executing a comprehensive suite of checks—including formatting verification, dead code detection, and dry-run builds—helping developers identify and resolve configuration errors before deployment.

Use Cases

  • Pre-deployment Verification: Validate NixOS configurations and flakes before applying changes to a system to prevent boot failures or configuration inconsistencies.
  • Automated Code Linting: Maintain high code quality by identifying syntax errors, dead code, and non-standard patterns within Nix expressions.
  • Flake Integrity Checks: Perform dry-run builds and flake-specific validations to ensure all inputs, outputs, and dependencies are correctly defined.
  • Continuous Integration Support: Use as a guided assistant to run formatting and linting scripts (fmt.sh, lint.sh) to ensure the codebase meets project standards.
  • Troubleshooting and Debugging: Quickly isolate issues in complex Nix setups by analyzing detailed error outputs and implementing suggested fixes for common formatting or logic errors.
namenix-check
descriptionCheck and validate NixOS configuration. Use when asked to check,

Nix Configuration Checker

When to Use

Use this skill when the user asks to check, validate, lint, or verify the nix configuration.

Instructions

Run the validation scripts in sequence:

  1. Format Check - Verify code formatting:

    ./scripts/fmt.sh --check
    
  2. Lint Check - Check for linting issues and dead code:

    ./scripts/lint.sh
    
  3. Flake Check - Validate flake and do a dry-run build:

    ./scripts/check.sh
    

Reporting Results

  • If all checks pass, report success
  • If any check fails, report which check failed and show the relevant error output
  • Suggest fixes for common issues (formatting can be auto-fixed with ./scripts/fmt.sh)