Run any Skill in Manus with one click

checking-nix-compat

Stars30

Forks1

UpdatedJuly 3, 2026 at 08:30

Use this skill when a nix change needs cross-platform or cross-architecture judgment before or after authoring. Trigger phrases include 'will this build on the mac', 'is this safe in a shared module', 'where should this module live', 'does this work on aarch64', 'check cross-platform compat', 'is this Linux-only'. Drives the judge-author-verify loop across nix-compat-checker, nix-config-architect, nix-checker, and nix-debugger. Does NOT cover general authoring with no placement/guard question (use creating-nix-modules instead) or diagnosing a failure unrelated to platform differences (use debugging-nix-failures instead).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

nicolkrit999

nicolkrit999/nix

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name

checking-nix-compat

description

Checking Nix Compat

The repo CLAUDE.md mandates delegating verification and debugging to agents - never run dry-builds or the test suite directly in the main loop. The orchestrator (this chat) dispatches each stage and loops; agents cannot call each other.

The loop

1. JUDGE - dispatch nix-compat-checker with the module or change in question. It decides correct placement (modules/common vs modules/nixos vs modules/darwin), whether Linux-only options in a shared module need lib.mkIf (moduleSystem == "nixos") guards, IFD-guard correctness, and x86_64 vs aarch64 differences. It can apply simple compat fixes (adding a guard, moving a small block) itself.

2. AUTHOR - dispatch nix-config-architect only if the judgment requires a placement move or non-trivial rework (splitting a module, restructuring options) beyond what the compat-checker applied directly. Pass it the compat-checker's judgment verbatim, not a paraphrase.

3. VERIFY - dispatch nix-checker for BOTH per-arch dry-builds (nixos-desktop toplevel for x86_64-linux AND Krits-MacBook-Pro system for aarch64-darwin) plus the arch-compat test in the templates/tests suite. Remind it Darwin needs --impure on nix flake check.

4. On failure - dispatch nix-debugger with the verbatim error from step 3, then loop back to step 3 to re-verify on the SAME checks. A fix for one platform can break the other, so always re-check both.

Loop 3 -> 4 until both platforms' dry-builds and the arch-compat test pass.

Safeguard: after ~4 rounds without convergence, stop and report the remaining issues to the user instead of continuing indefinitely.

Exit condition

Both platforms' dry-builds green AND the arch-compat test passes. Report to the user what moved (if anything), what guards were added or confirmed correct, and why.

Out of scope

General module authoring with no cross-platform question at stake - that's creating-nix-modules.
Diagnosing a failure that isn't about platform/arch differences (e.g. a typo'd option name, a missing package) - that's debugging-nix-failures.

More from this repository

same repository

investigating-nix-issues

nicolkrit999/nix

Use this skill for general debugging of this nix config whenever it is NOT already known that a build/flake check/rebuild is failing - runtime or boot-time misbehavior, hardware quirks driven by config, config that silently doesn't take effect, code that looks broken but builds, suspected dead/orphaned code, an unresolved issue recorded in a memory file, or any vague observation that something is off. The issue can come from existing code, a memory entry, or a user report alike. Trigger phrases include 'debug this', 'something is wrong with X', 'it builds but doesn't work', 'X stopped working after a successful rebuild', 'this option seems to have no effect', 'is this module even used', 'find dead code', 'look into that unresolved issue from memory', 'retry the fix we reverted', 'debug why X behaves like this'. Drives the frame-investigate-fix-verify loop across nix-debugger, nix-config-architect, nix-package-researcher, nix-checker, and Explore. Does NOT cover a KNOWN-failing build/flake check/rebuild (use d

2026-07-0330

creating-nix-modules

nicolkrit999/nix

Use this skill when adding or modifying nix configuration that introduces new functionality, such as new denix modules, enabling programs/services, host constants, theming, or home-manager config. Trigger phrases include 'add a module', 'enable X on host Y', 'install/integrate package Z', 'configure <service> in nix', 'add this to my nixos config', 'set up <program> via home-manager'. Drives the research-author-lint-verify pipeline across nix-package-researcher, nix-config-architect, nix-syntax-linter, and nix-checker. Does NOT cover diagnosing an existing build failure (use debugging-nix-failures instead) or pure attribute/option lookups with no authoring (dispatch nix-package-researcher directly).

2026-07-0330

adding-nix-tests

nicolkrit999/nix

Use this skill when new or improved test coverage is needed for a nix module or behavior. Trigger phrases include 'add a test for this module', 'improve test coverage', 'write a test that X', 'register this test', 'test the new module', 'cover this with a test'. Drives the author-run-triage loop across nix-test-author, nix-checker, and nix-debugger. Does NOT cover merely running the existing suite with no new test (dispatch nix-checker directly instead) or authoring non-test config (use creating-nix-modules instead).

2026-07-0330

debugging-nix-failures

nicolkrit999/nix

Use this skill when a nix build, flake check, nixos-rebuild, or darwin-rebuild is failing and needs to be diagnosed and fixed. Trigger phrases include 'the build failed', 'flake check fails', 'nixos-rebuild broke', 'why won't it evaluate', 'fix this nix error', 'option does not exist', 'darwin-rebuild is erroring', 'my rebuild is broken'. Drives the reproduce-diagnose-fix-reverify loop across nix-checker and nix-debugger. Does NOT cover authoring new functionality (use creating-nix-modules instead) or pure style/format sweeps with no build failure (dispatch nix-syntax-linter directly).

2026-07-0330

name

checking-nix-compat

description

Checking Nix Compat

The loop

Loop 3 -> 4 until both platforms' dry-builds and the arch-compat test pass.

Safeguard: after ~4 rounds without convergence, stop and report the remaining issues to the user instead of continuing indefinitely.

Exit condition

Both platforms' dry-builds green AND the arch-compat test passes. Report to the user what moved (if anything), what guards were added or confirmed correct, and why.

Out of scope

General module authoring with no cross-platform question at stake - that's creating-nix-modules.
Diagnosing a failure that isn't about platform/arch differences (e.g. a typo'd option name, a missing package) - that's debugging-nix-failures.