Bridge non-flake Nix code with flake tooling using overlay.nix and flake-compat.
npx skills add https://github.com/Jylhis/skills --skill nix-hybrid
Please help me install this Agent Skill. Skill: nix-hybrid Source: https://github.com/Jylhis/skills/tree/main/skills/nix-hybrid Command: npx skills add https://github.com/Jylhis/skills --skill nix-hybrid
Hybrid Nix projects often juggle non-flake code with flake-based tooling, causing architectural confusion and pinning drift; nix-hybrid provides patterns and guidance to reconcile these approaches for predictable builds.
Explain how to set up a hybrid Nix project by wiring an overlay.nix with a flake.nix orchestrator and enabling a flake-compat shim for non-flake consumers.
High-intent search queries and answers about installing and using this skill.
To bridge non-flake code with flake tooling for reliable Nix builds, wire an overlay.nix with a flake.nix orchestrator and enable a flake-compat shim for non-flake consumers. This maintains parity and safe operation across hybrid workflows.
The best way to keep flake.lock and devenv.lock pins synchronized is to apply pin synchronization techniques and devenv integration patterns. This ensures both lock files remain aligned, preventing pinning drift in hybrid Nix projects.
Yes, you can use an overlay.nix architecture alongside a flake.nix orchestrator. This hybrid Nix project setup supports both package and module patterns while maintaining compatibility with existing non-flake workflows.
You need a flake-compat shim to support non-flake consumers in a NixOS or nix-darwin project. It bridges the gap between flake-based tooling and non-flake code, ensuring predictable builds without forcing consumers to adopt flakes.
Pinning drift happens in hybrid Nix projects when non-flake code and flake-based tooling juggle separate lock files without synchronization. Prevent it by applying pin synchronization patterns to keep flake.lock and devenv.lock aligned.
To migrate a Nix project toward a unified hybrid workflow, apply migration patterns that integrate overlay.nix, module and package flakes, and devenv tooling. This preserves compatibility with existing non-flake workflows while reconciling architectural confusion.
OmegaiceConvert Nix flakes to modular flake-parts structures with perSystem outputs.
ciUpdate Nix flake inputs and verify with nix flake check.
cgeorgiiReference NixOS build, test, and flake commands for system configuration tasks.
knoopxInitialize and manage reproducible Nix flakes with nix flake commands.
