nix-command

Map legacy Nix commands to unified nix subcommands.

3|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/ncaq/konoka --skill nix-command
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nix-command
Source: https://github.com/ncaq/konoka/tree/main/plugins/nix-tasuke/skills/nix-command
Command: npx skills add https://github.com/ncaq/konoka --skill nix-command

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns teams with the unified Nix CLI by de-emphasizing legacy commands (nix-build, nix-env, nix-shell) in favor of nix subcommand usage, reducing confusion and accelerating workflows.

Core Features & Use Cases

  • Provides clear mappings from old commands to new nix subcommand equivalents for build, development, package management, and environment operations.
  • Documents recommended command structures, syntax conventions, and best practices for common Nix workflows.
  • Serves as an onboarding reference for teams upgrading to the latest CLI practices and for scripting automation that relies on Nix.

Quick Start

Replace legacy nix commands with their new nix subcommand equivalents in your daily usage.

Frequently Asked Questions about nix-command

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from nix-build and nix-env to the new unified nix CLI?

To migrate from legacy nix-build and nix-env commands to the unified nix CLI, replace them with equivalent nix subcommands like nix build and nix profile. This transition reduces confusion by standardizing syntax conventions and accelerating development and operations workflows.

What is the recommended replacement for nix-shell in modern Nix workflows?

The recommended replacement for nix-shell in modern Nix workflows is using the new nix subcommand equivalents. Adopting the unified nix CLI ensures teams follow current best practices, replacing legacy command structures with standardized development environment operations.

How does the unified nix subcommand improve DevOps automation scripting?

The unified nix subcommand improves DevOps automation scripting by providing a consistent command structure. Replacing fragmented legacy commands with standardized nix subcommands reduces syntax confusion and ensures scripting automation reliably follows modern best practices.

Can I use the new nix subcommands for both local development and operations package management?

Yes, you can use the new nix subcommands for both local development and operations package management. The unified nix CLI provides clear command mappings for build, development, environment, and package management operations across team workflows.

What are the best practices for transitioning a team to the modern Nix CLI?

Best practices for transitioning a team to the modern Nix CLI involve using the unified nix subcommand structure as an onboarding reference. Teams should replace legacy commands like nix-build with nix build equivalents to ensure consistent syntax conventions and faster workflows.