cli-just
This skill should be used when the user asks to "create a justfile", "write just recipes", "configure just settings", "add just modules", "use just attributes", "set up task automation", mentions justfile, just command runner, or task automation with just.
What this skill does
# Just Command Runner
## Overview
Expert guidance for Just, a command runner with syntax inspired by make. Use this skill for creating justfiles, writing recipes, configuring settings, and implementing task automation workflows.
**Key capabilities:**
- Create and organize justfiles with proper structure
- Write recipes with attributes, dependencies, and parameters
- Configure settings for shell, modules, and imports
- Use built-in constants for terminal formatting
- Implement check/write patterns for code quality tools
## Quick Reference
### Essential Settings
```just
set allow-duplicate-recipes # Allow recipes to override imported ones
set allow-duplicate-variables # Allow variables to override imported ones
set shell := ["bash", "-euo", "pipefail", "-c"] # Strict bash with error handling
set unstable # Enable unstable features (user-defined functions, eager keyword)
set dotenv-load # Auto-load .env file
set positional-arguments # Pass recipe args as $1, $2, etc.
set lazy # Defer evaluation of unused variables (v1.48.0+)
set no-cd # Don't change to justfile directory for any recipe (v1.51.0+)
set default-list := true # Bare `just` lists recipes instead of running default (v1.52.0+)
set default-script := true # Make unannotated recipes script recipes; use sparingly (v1.52.0+)
```
### Common Attributes
| Attribute | Purpose |
| -------------------------- | -------------------------------------------------------------- |
| `[arg("p", long, ...)]` | Configure parameter as `--flag` option (v1.46) |
| `[arg("p", pattern="…")]` | Constrain parameter to match regex pattern |
| `[confirm("prompt")]` | Require user confirmation (expressions OK as of v1.49) |
| `[doc("text")]` | Override recipe documentation |
| `[env("NAME", "VALUE")]` | Set env var for this recipe only (v1.47+, expr v1.51) |
| `[group("name")]` | Group recipes in `just --list` output |
| `[linux]` / `[macos]` … | Restrict to OS; also `[android]` (v1.50+) and BSD variants |
| `[no-cd]` | Don't change to justfile directory |
| `[parallel]` | Run direct dependencies concurrently |
| `[positional-arguments]` | Enable positional args for this recipe only |
| `[private]` | Hide from `just --list` (same as `_` prefix) |
| `[script]` | Execute recipe as single script block |
| `[script("interpreter")]` | Use specific interpreter (bash, python, etc.) |
| `[shell]` | Force linewise shell mode when `set default-script` is enabled |
| `[working-directory: "…"]` | Run from given path (expressions OK as of v1.51) |
### Recipe Argument Flags (v1.46.0+)
The `[arg()]` attribute configures parameters as CLI-style options:
```just
# Long option (--target)
[arg("target", long)]
build target:
cargo build --target {{ target }}
# Short option (-v)
[arg("verbose", short="v")]
run verbose="false":
echo "Verbose: {{ verbose }}"
# Combined long + short
[arg("output", long, short="o")]
compile output:
gcc main.c -o {{ output }}
# Flag without value (presence sets to "true")
[arg("release", long, value="true")]
build release="false":
cargo build {{ if release == "true" { "--release" } else { "" } }}
# Help string (shown in `just --usage`)
[arg("target", long, help="Build target architecture")]
build target:
cargo build --target {{ target }}
```
**Usage examples:**
```bash
just build --target x86_64
just build --target=x86_64
just compile -o main
just build --release
just --usage build # Show recipe argument help
```
Multiple attributes can be combined:
```just
[no-cd, private]
[group("checks")]
recipe:
echo "hello"
```
### Built-in Constants
Terminal formatting constants are globally available (no definition needed):
| Constant | Description |
| --------------------------------------------------- | ------------------------------------------ |
| `CYAN`, `GREEN`, `RED`, `YELLOW`, `BLUE`, `MAGENTA` | Text colors |
| `BOLD`, `ITALIC`, `UNDERLINE`, `STRIKETHROUGH` | Text styles |
| `NORMAL` | Reset formatting |
| `BG_*` | Background colors (BG_RED, BG_GREEN, etc.) |
| `HEX`, `HEXLOWER`, `HEXUPPER` | Hexadecimal digits |
Usage:
```just
@status:
echo -e '{{ GREEN }}Success!{{ NORMAL }}'
echo -e '{{ BOLD + CYAN }}Building...{{ NORMAL }}'
```
### Key Functions
```just
# Require executable exists (fails recipe if not found)
jq := require("jq")
# Get environment variable with default
log_level := env("LOG_LEVEL", "info")
# Get justfile directory path
root := justfile_dir()
# Module location (useful inside `mod` files)
mod_path := module_path() # Full submodule path, e.g. "foo::bar"
mod_file := module_file() # Absolute path to module's justfile
mod_dir := module_directory() # Directory containing the module justfile
# Runtime directory (v1.49.0; typically $XDG_RUNTIME_DIR, falls back to tempdir)
rt := runtime_directory()
```
### User-Defined Functions (v1.49.0+)
Define reusable named expressions with `name(args) := expression`. Requires `set unstable`. Functions can reference module-level assignments.
```just
set unstable
base := "foo"
join(extension) := base + "." + extension
# Use f-strings for interpolation
hello(name) := f"Hello, {{ name }}!"
create:
touch {{ join("c") }}
touch {{ join("html") }}
echo '{{ hello("World") }}'
```
Use these to dedupe expression logic that would otherwise repeat across recipes; prefer them over backtick-evaluated variables when the value depends on input.
## Recipe Patterns
When designing recipes that use status reporting, check/write semantics, or alias conventions, see [references/patterns.md](references/patterns.md).
## Inline Scripts
When writing recipes that need shell scripts (script attribute or shebang style), see [references/inline-scripts.md](references/inline-scripts.md).
## Modules & Imports
### Import Pattern
Include recipes from another file:
```just
import "./just/settings.just"
import "./just/base.just"
import? "./local.just" # Optional (no error if missing)
```
### Module Pattern
Load submodule (requires `set unstable`):
```just
mod foo # Loads foo.just or foo/justfile
mod bar "path/to/bar" # Custom path
mod? optional # Optional module
# Call module recipes
just foo::build
```
### Devkit Import Pattern
For projects using `@sablier/devkit`:
```just
import "./node_modules/@sablier/devkit/just/base.just"
import "./node_modules/@sablier/devkit/just/npm.just"
```
## Section Organization
Standard section header format:
```just
# ---------------------------------------------------------------------------- #
# DEPENDENCIES #
# ---------------------------------------------------------------------------- #
```
Common sections (in order):
1. **DEPENDENCIES** - Required tools with URLs
2. **CONSTANTS** - Glob patterns, environment vars
3. **RECIPES / COMMANDS** - Main entry points
4. **CHECKS** - Code quality recipes
5. **UTILITIES / INTERNAL HELPERS** - Private helpers
## Default Recipe
Define a curated default recipe when one action should be the entrypoint:
```just
# Run all checks by default
defRelated in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.