Skip to content
Back to skills

Nix Justfile

ASecurity

Conventions for writing justfile recipes in Nix-based projects.

  • 11 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
toolsgoshellnode

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add juspay/skills --skill nix-justfile --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Nix Justfile?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Nix Justfile
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/juspay-nix-justfile-skills/badge)](https://www.skillsdirectory.com/skills/juspay-nix-justfile-skills)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: nix-justfile
description: Conventions for writing justfile recipes in Nix-based projects.
---

# Justfile in Nix projects

## Doc comments

Every recipe must have a doc comment (`#` line above the recipe name).

## Devshell detection

Use a `nix_shell` variable to auto-detect whether we're inside `nix develop`:

```just
nix_shell := if env('IN_NIX_SHELL', '') != '' { '' } else { 'nix develop -c' }
```

Prefix commands that need devshell tools (node, trunk, cargo-watch, etc.) with `{{nix_shell}}`. Recipes that invoke `nix` directly (build, run, flake commands) don't need it.

## Legibility

Long chained commands should use multiline `\` continuations.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…