@rcrsr/rill-cli

Command-line tools for running and validating rill scripts.

> Experimental. Breaking changes will occur before stabilization.

Install

``bash
npm install -g @rcrsr/rill-cli
`

Tools

$3

Execute a rill script file.

`bash
rill-exec script.rill [args...]
rill-exec - # read from stdin
`

Positional arguments pass to the script as $ARGS:

`bash
rill-exec greet.rill alice bob


Inside script: $ARGS == ["alice", "bob"]


`

Read from stdin with -:

`bash
echo '"Hello" -> log' | rill-exec -
`

Exit codes:

| Return Value | Exit Code |
|-------------|-----------|
| true or non-empty string | 0 |
| false or empty string | 1 |
| [0, "message"] | 0 (prints message) |
| [1, "message"] | 1 (prints message) |

$3

Evaluate a single rill expression. No file context or module loading.

`bash
rill-eval '"hello".len' # 5
rill-eval '5 + 3' # 8
rill-eval '[1, 2, 3] -> map |x|($x * 2)' # [2, 4, 6]
`

$3

Lint and validate rill scripts.

`bash
rill-check script.rill # text output
rill-check --format json script.rill
rill-check --fix script.rill # auto-fix
`

Options:

| Flag | Description |
|------|-------------|
| --fix | Apply automatic fixes |
| --format text\|json | Output format (default: text) |
| --verbose | Include rule category in JSON output |

Exit codes:

| Code | Meaning |
|------|---------|
| 0 | No issues |
| 1 | Diagnostics reported |
| 2 | File not found |
| 3 | Parse error |

Configuration: Place .rill-check.json in the project root:

`json
{
"rules": {
"NAMING_SNAKE_CASE": "on",
"SPACING_OPERATOR": "off"
}
}
`

Rule states: "on" (enabled), "off" (disabled), "warn" (downgrade to warning).

Lint rules: 30 rules across 8 categories (naming, anti-patterns, strings, types, flow, loops, collections, formatting). Run rill-check --help` for the full list.

Documentation

| Document | Description |
|----------|-------------|
| CLI Reference | Full CLI documentation |
| Language Reference | Language specification |
| Conventions | Coding style and lint rationale |

License

MIT