Rexo.Cli 0.3.2

Rexo CLI (rx)

Rexo is a config-driven repository automation CLI. It runs the same workflow model locally and in CI from a repository config file.

Install

dotnet tool install --global Rexo.Cli

To update:

dotnet tool update --global Rexo.Cli

Run Without Installing (dnx)

If you prefer not to install globally, run Rexo directly from NuGet:

dotnet dnx Rexo.Cli -- --help
dotnet dnx Rexo.Cli -- init --yes --stack auto

Use -- after Rexo.Cli so remaining arguments are passed to rx.

Quick Start

1. Run rx init (defaults to .rexo/rexo.json).
2. Add commands and steps.
3. Run commands with rx. Example:

rx init
rx list

Non-interactive example with policy:

rx init --yes --stack auto --with-policy --policy dotnet

By default, init uses a local schema file to avoid editor trust prompts:

rx init --yes --schema-source local

Use remote schema URL instead:

rx init --yes --schema-source remote

Non-interactive example that also downloads AI instructions into the repo:

rx init --yes --with-instructions

Custom destination for instructions file:

rx init --yes --with-instructions --instructions-path .github/instructions/rexo.instructions.md

Docker artifact scaffolding

When rx init detects a Dockerfile in the repository, it automatically scaffolds a minimal docker artifact in the generated config (defaulting to yes in interactive mode, and opting in automatically in non-interactive mode). To opt out in non-interactive mode:

rx init --yes --without-docker-artifact

To force docker artifact scaffolding even when no Dockerfile is detected:

rx init --yes --with-docker-artifact

--with-docker-artifact and --without-docker-artifact cannot be combined — passing both is an error. Minimal example:

{
"$schema": "https://raw.githubusercontent.com/agile-north/rexo/schema/v1.0/rexo.schema.json",
"schemaVersion": "1.0",
"name": "my-repo",
"commands": {
"build": {
"description": "Build the project",
"options": {},
"steps": [
{ "run": "dotnet build -c Release" }
]
}
},
"aliases": {}
}

Run it:

rx build

Common Commands

rx list
rx explain build
rx config sources
rx config resolved --json
rx doctor

Configuration Discovery

Rexo looks for configuration in this order:

1. rexo.json, rexo.yaml, rexo.yml
2. .rexo/rexo.json, .rexo/rexo.yaml, .rexo/rexo.yml
3. Backward-compatible fallback: repo.json|yaml|yml (root and .repo/) Policy files are discovered in root, .rexo/, and legacy .repo/ locations.

Notes

• Use rx directly to run configured commands.
• Use rx run <command> if you want explicit run semantics.
• Use --json or --json-file <path> for machine-readable output.
• Full JSON and manifest field semantics: Output Contract.

Documentation

AI assistant tip: rx init --with-instructions downloads rexo.instructions.md into .github/instructions/rexo.instructions.md by default. Use --instructions-path to choose another repo-relative destination.