with one click
testing
Test changes using module-graph and build commands
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.
Menu
Test changes using module-graph and build commands
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.
Based on SOC occupation classification
Create and modify NixOS and Home-Manager modules
Hardens systemd services against security issues using sandboxing, capability restriction, and syscall filtering. Use when creating or modifying systemd services, writing NixOS modules with systemd.services, reviewing service security, or whenever a serviceConfig block is involved. Ensures services follow defense-in-depth principles with minimal privilege.
Write Nix code using repo conventions
Write and review Conventional Commits commit messages (v1.0.0) for semantic versioning and changelogs. Use when drafting git commit messages, PR titles, release notes, or enforcing conventional commit format like `type(scope): subject`, `BREAKING CHANGE`, footers, and `revert`.
Manages version control with Jujutsu (jj), including rebasing, conflict resolution, and Git interop. Use when tracking changes, navigating history, squashing/splitting commits, or pushing to Git remotes.
Manage background jobs, capture command output, and handle session multiplexing. Use when running long commands, capturing output from detached processes, or managing concurrent tasks in headless environments.
| name | testing |
| description | Test changes using module-graph and build commands |
After making changes you must always evaluate and test them.
Use module-graph script to find which hosts and homes are affected by changed files:
./flake/dev/scripts/module-graph.nu
This outputs JSON showing which configs use each file:
{
"file": "modules/nixos/services/tailscale.nix",
"hosts": ["nixdev", "nixmi", "nixcloud"],
"homes": []
}
Based on module-graph output, test at least one of each affected type:
| Changed File Affects | Minimum Test |
|---|---|
| Hosts only | Build one affected host |
| Homes only | Build one affected home |
| Both hosts and homes | Build one host and one home |
nix build .#nixosConfigurations.<hostname>.config.system.build.toplevel
nix build .#homeConfigurations."<user>@<host>".activationPackage
nix flake check --override-input devenv-root "file+file://$PWD/.devenv/root"
Make changes to modules/nixos/services/tailscale.nix
Run module-graph to find affected configs:
./flake/dev/scripts/module-graph.nu | jq '.[] | select(.file | contains("tailscale"))'
Pick one affected host and build it:
nix build .#nixosConfigurations.nixdev.config.system.build.toplevel
If change also affects homes, build one:
nix build .#homeConfigurations."racci@nixmi".activationPackage