policy:
  allow_implicit_invocation: true

# Inline Scripts

> Read when a recipe needs multi-line shell or another interpreter. Confirm the installed syntax with `just --help`,
> `just --man`, or the current manual before adding an attribute or setting.

Use linewise recipes for short commands. Use `[script("interpreter")]` or a shebang when the body needs shell state,
traps, control flow, or a non-shell language. `set default-script` changes the default; `[shell]` opts one recipe back
to linewise execution.

```just
[script("bash")]
deploy:
    set -e
    ./build.sh
    ./deploy.sh
```

Script recipes are quiet already. Do not prefix a `[script]` recipe with `@`: there it prints the generated script body.
See [recipes.md](recipes.md#quiet-recipes-and-command-prefixes) for linewise echo rules.

## Bash on macOS

Assume `/bin/bash` 3.2 unless the recipe selects another shell. Write 3.2-compatible bodies by default; pin a newer
interpreter only for semantics that require it, and ensure that path is available in CI and agent environments.

```just
set shell := ["/opt/homebrew/bin/bash", "-euo", "pipefail", "-c"]
```

For a Bash-4+-only recipe, guard before using its newer syntax:

```just
[script("bash")]
modern:
    if [ "${BASH_VERSINFO[0]}" -lt 4 ]; then
        echo "error: bash >= 4 required (found $BASH_VERSION)" >&2
        exit 1
    fi
    declare -A map=([a]=1)
```

# Justfile Patterns & Conventions

Match the existing justfile's banner, grouping, recipe order, aliases, and default behavior. For a new standalone file,
start from the linked [standalone template](../examples/standalone.just) or [devkit template](../examples/devkit.just)
for its task-runner shape. Put aliases adjacent to their target. Keep an explicit `just --list` default for older or
established layouts.

Use small recipes and private prerequisites. Offer check/write pairs for mutable operations and run the check path
before the write path when practical. Group list output only when it improves the repository's existing organization.

Use `[no-cd]`, a working directory, or an OS guard only when the recipe's execution contract needs it.

# Just Recipes Reference

> Read for recipe shape, dependencies, parameters, attributes, or command echoing. Discover version-sensitive syntax
> from the installed `just --help`, `just --man`, or current manual before writing it.

Keep recipes explicit and short. Use parameters and dependencies only when they make the invocation clearer; make a
helper private when it is not an intended entrypoint. Scope environment variables, working directories, OS restrictions,
confirmations, grouping, and parallelism to the recipe that needs them.

## Native executable checks

Use Just-native checks instead of shell `command -v` or backtick `which`. When the justfile already enables the needed
`set unstable` and `set lists`, `which()` with `assert()` can give an actionable install message. Otherwise use
`require()` when its standard missing-executable error is enough. Put the assertion at top level only if every recipe
needs the tool; otherwise put it in a private prerequisite of affected recipes.

## Quiet recipes and command prefixes

Make ordinary recipes quiet with `@recipe:` when echoed commands add no value. In a quiet recipe, a line-level `@`
inverts that choice and deliberately echoes that line, so leave lines unprefixed by default. In a non-quiet recipe,
line-level `@` suppresses one command; `-` ignores one command error. See [inline-scripts.md](inline-scripts.md) for
script echoing.

```just
@check:
    cargo test
    @echo "this command is deliberately echoed"
```

# Just Settings & Modules Reference

> Read for global configuration, dotenv behavior, lists, imports, or modules. Verify every setting against the installed
> `just --help`, `just --man`, or current manual.

Put settings before imports and recipes. Preserve the repository's existing choices for shell, dotenv, fallback,
quietness, module layout, and duplicate definitions. Put shared imports first and local or optional overrides last.

For an unstable feature, check whether it also requires a companion setting such as `set lists`. Lists represent
collections of distinct values; parenthesized string concatenation builds one string.

For the exact setting name, module path syntax, dotenv precedence, and version gate, inspect the installed manual.

# Just Syntax Reference

> Read for expressions, functions, constants, interpolation, or version-gated syntax. Prefer the installed manual:
> `just --help`, `just --man`, or the current online manual.

Evaluate shell work only when Just cannot express it directly. For the collection-versus-string distinction, see
[settings.md](settings.md).

Place `set minimum-version` at the very top, before features it guards. The check runs in the parser; incompatible lexer
syntax can still fail before that check. Confirm the feature's introduction version and choose compatible syntax or
raise the repository's minimum version. See the
[minimum-version manual](https://just.systems/man/en/requiring-a-minimum-just-version.html).

1.58.0