What problem does it solve? Changing flake inputs or external packages in a NixOS flake repository risks broad lockfile churn, broken follows relationships, architecture regressions, and unclear ownership between overlays, modules, and consumers. This Skill enforces a disciplined workflow for adding, pinning, updating, or removing inputs safely. ## Core Features & Use Cases - Controlled input changes: Traces each input through flake.nix, flake.lock, module package options, and host/Home Manager consumers before editing. - Authorization gating: Requires explicit approval before mutating flake.lock, running network-fetching commands, or accepting unexpected transitive churn. - Architecture-aware validation: Evaluates every affected nixosConfigurations toplevel for both x86_64-linux and aarch64-linux targets, plus just chk and diff checks. - Use Case: When adding a new external flake package to the GTR7 desktop and Pi4B homelab, the Skill selects the correct integration path (module import, direct package consumption, or typed package option), reconciles the lock narrowly, and validates both architectures. ## Quick Start Use the nixcf-flake-package skill to add a new flake input and wire its package into the Pi4B Home Manager profile without touching unrelated lock entries.
