Skip to content
Skills Library
Programming · Learning & explanation

cli-reference

/cli-reference

Documents the human-facing axvs command-line interface. Covers every command and option with its short form, long form, type, default, and effect, the MCP tool each command maps to, its failure modes, and how the CLI path diverges from the MCP path. Use when a user asks what an axvs command or option does, or when the MCP server is unavailable and the user must be told what to run by hand.

Repository
ataraxis ↗
Licence
Apache-2.0
Last repository change
28.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.09.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Documents the human-facing axvs command-line interface. Covers every command and option with its short form, long form, type, default, and effect, the MCP tool each command maps to, its failure modes, and how the CLI path diverges from the MCP path. Use when a user asks what an axvs command or option does, or when the MCP server is unavailable and the user must be told what to run by hand.

Original author description

Documents the human-facing axvs command-line interface. Covers every command and option with its short form, long form, type, default, and effect, the MCP tool each command maps to, its failure modes, and how the CLI path diverges from the MCP path. Use when a user asks what an axvs command or option does, or when the MCP server is unavailable and the user must be told what to run by hand.

How it works

  1. Scope
  2. Agent requirements
  3. Command surface
  4. Option reference
  5. Command behavior and failure modes
  6. Fallback: what to tell a user when MCP is unavailable
  7. Related skills
  8. Verification checklist
Original SKILL.md headings · 356 lines, 3,602 words
SKILL.md preview
---
name: cli-reference
description: >-
  Documents the human-facing axvs command-line interface. Covers every command and option with its short form,
  long form, type, default, and effect, the MCP tool each command maps to, its failure modes, and how the CLI
  path diverges from the MCP path. Use when a user asks what an axvs command or option does, or when the MCP
  server is unavailable and the user must be told what to run by hand.
user-invocable: false
---

# CLI reference

> **The `axvs` CLI is a HUMAN-FACING tool. You MUST never invoke it.** Print the command, ask the user to run it, and
> ask them to paste the output back.

**The one exemption** is `--help`. `axvs --help` and `axvs COMMAND --help` may be run, and no other `axvs` invocation is
exempt. `/video-mcp-environment-setup` owns that exemption.

---

## Scope

**Covers:**
- The complete `axvs` command surface: every node, its purpose, and its MCP equivalent
- Every declared option: short form, long form, type, default, required / flag / repeatable status, and effect
- Per-command failure modes and the exception each raises
- How `axvs run` diverges from an MCP video session, and how `axvs process` diverges from the MCP batch
- What to tell a user to run when the MCP server cannot be restored in this session

**Does not cover:**
- The MCP session tools, GenICam tools, and manifest tools (see `/camera-setup`)
- The MCP batch workflow, lenient sourcing, and resource sizing (see `/log-processing`)
- Writing VideoSystem code, which no `axvs` command replaces (see `/camera-interface`)
- Diagnosing why the MCP server is down (see `/video-mcp-environment-setup`)
- Driving log processing from Python. The library exports its orchestration symbols, but they are not an agent-facing
  surface, so never drive a batch from Python

**Handoff rules:** If the user wants an operation performed, use the MCP tools and invoke the owning skill. If the MCP
tools are unavailable, invoke `/video-mcp-environment-setup` first and fall back to the CLI-command handoff table below
only after the server cannot be restored.

---

## Agent requirements

You MUST answer CLI questions from this skill or from `axvs --help`, never from memory. When a user's report disagrees
with this reference, ask them to run `axvs COMMAND --help` and read the installed build's answer.

---

## Command surface

The CLI declares fifteen Click nodes: the root group, three subgroups, and eleven leaf commands. The entry point is
`axvs = "ataraxis_video_system.interfaces.cli:axvs_cli"`.

| Click node                 | Kind    | Purpose                                                           | MCP equivalent                    |
|----------------------------|---------|-------------------------------------------------------------------|-----------------------------------|
| `axvs`                     | group   | Entry point. Dispatches to the subcommands and prints the listing | None, dispatch only               |
| `axvs cti`                 | group   | Dispatches the GenTL Producer (`.cti`) file subcommands           | None, dispatch only               |
| `axvs cti set`             | command | Configures the GenTL Producer file used by every future runtime   | `set_cti_file_tool`               |
| `axvs cti check`           | command | Reports whether a valid Producer file is configured               | `get_cti_status_tool`             |
| `axvs check`               | group   | Dispatches the discovery and host-compatibility subcommands       | None, dispatch only               |
| `axvs check devices`       | command | Discovers cameras on both interfaces and prints their indices     | `list_cameras_tool`               |
| `axvs check compatibility` | command | Reports FFMPEG and NVIDIA GPU video-encoding support              | `check_runtime_requirements_tool` |
| `axvs run`                 | command | Runs an interactive single-camera imaging session                 | The session tools, see below      |
| `axvs process`             | command | Extracts frame timestamps from ONE log directory's archives       | The batch tools, see below        |
| `axvs mcp`                 | command | Starts the MCP server                                             | None, this command IS the server  |
| `axvs configure`           | group   | Dispatches the GenICam configuration subcommands                  | None, dispatch only               |
| `axvs configure read`      | command | Reads one GenICam node or lists every writable GenICam node       | `read_genicam_node_tool`          |
| `axvs configure write`     | command | Writes a value to one GenICam node                                | `write_genicam_node_tool`         |
| `axvs configure dump`      | command | Exports the camera's full configuration to a YAML file            | `dump_genicam_config_tool`        |
| `axvs configure load`      | command | Applies a YAML configuration file to the camera                   | `load_genicam_config_tool`        |

`axvs run` maps to `start_video_session_tool`, `start_frame_saving_tool`, `stop_frame_saving_tool`, and
`stop_video_session_tool` taken together. `axvs process` maps to `prepare_log_processing_batch_tool` and
`execute_log_processing_jobs_tool` taken together. Both mappings carry the divergences documented below.

**Note:** Twenty-five options are declared across the surface. Click adds `--help` to every node on top of those. The
CLI leaves `help_option_names` at its `["--help"]` default, so `-h` is never a help alias. On `axvs run`, `-h` is bound
to `--height` and consumes the next token as a pixel count, so `axvs run -h` fails on the missing value.

---

## Option reference

Every option below is declared in `interfaces/cli.py`. "Required" means Click rejects the invocation without it (exit
code 2). Path options carry Click `click.Path` constraints, listed under Effect.

### `axvs cti set`

| Short | Long          | Type   | Default    | Form     | Effect                                                            |
|-------|---------------|--------|------------|----------|-------------------------------------------------------------------|
| `-f`  | `--file-path` | `Path` | (required) | required | The vendor `.cti` Producer to persist. Must exist and be readable |

`axvs cti check` and both `axvs check` subcommands declare no options of their own.

### `axvs run`

| Short | Long                 | Type     | Default    | Form     | Effect                                                                   |
|-------|----------------------|----------|------------|----------|--------------------------------------------------------------------------|
| `-i`  | `--interface`        | `Choice` | `"mock"`   | optional | Camera interface. Choice of `mock`, `harvesters`, and `opencv`           |
| `-c`  | `--camera-index`     | `int`    | `0`        | optional | Index of the camera within the chosen interface's discovery listing      |
| `-g`  | `--gpu-index`        | `int`    | `-1`       | optional | GPU device for encoding. Any value below zero selects CPU encoding       |
| `-o`  | `--output-directory` | `Path`   | (required) | required | Where the `.mp4` and the log directory are written. Must already exist   |
| `-m`  | `--monochrome`       | flag     | `False`    | flag     | Records grayscale. Applies to `opencv` and `mock` only, never Harvesters |
| `-w`  | `--width`            | `int`    | `600`      | optional | Frame width in pixels                                                    |
| `-h`  | `--height`           | `int`    | `400`      | optional | Frame height in pixels. **This is why `-h` is not a help alias**         |
| `-f`  | `--frame-rate`       | `int`    | `30`       | optional | Acquisition rate in frames per second                                    |

**Note on `-i`:** the default is `mock`, which produces synthetic frames and touches no hardware. A user testing a real
camera must name `opencv` or `harvesters` explicitly, so always include the option in a command handed to a user.

**Note on `-o`:** Click requires the directory to exist already, unlike `axvs process -od`. A user pointing at a path
they have not created yet is rejected at exit code 2 before the session starts.

### `axvs process`

| Short | Long                 | Type   | Default    | Form       | Effect                                                                            |
|-------|----------------------|--------|------------|------------|-----------------------------------------------------------------------------------|
| `-ld` | `--log-directory`    | `Path` | (required) | required   | The ONE DataLogger output directory, searched recursively for `.npz` archives     |
| `-od` | `--output-directory` | `Path` | (required) | required   | The output root. A `camera_timestamps/` subdirectory holding every output is made |
| `-id` | `--job-id`           | `str`  | `None`     | optional   | Runs ONLY the job whose hexadecimal identifier matches. Suppresses `-s`           |
| `-s`  | `--specifier`        | `str`  | `()`       | repeatable | A camera source ID to process. Repeat once per camera. Ignored when `-id` is set  |
| `-w`  | `--workers`          | `int`  | `-1`       | optional   | The workers ONE job receives, not a batch width. See the note                     |
| `-np` | `--no-progress`      | flag   | `False`    | flag       | Suppresses the extraction progress bars. Bars are displayed by default            |

**Note on `-s`:** when omitted, every source the recording's `camera_manifest.yaml` registers is processed. Each named
ID must be registered in that manifest and must resolve to exactly one archive beneath `-ld`.

**Note on `-w`:** a positive value reaches every job verbatim, so `-w 1` makes every job sequential. An archive holding
fewer messages than the archive reader's own parallel processing threshold still runs sequentially whatever width it
was handed, so a higher `-w` buys a small archive nothing. The `-1` default resolves each job's width from its own
archive instead, which is one worker for an archive below the library's parallel extraction threshold and the declared
per-job allocation at or above it. That default is the same width rule the MCP batch applies, before the batch
collapses it onto a core budget this path has none of, so the explicit value is the whole divergence.

**Note on `-id`:** a job identifier is a deterministic function of the job name and the camera's `source_id`, so one
camera keeps the same identifier across recordings. A user obtains it from the `job_id` key of a
`prepare_log_processing_batch_tool` job entry, or from the tracker YAML.

### `axvs mcp`

| Short | Long          | Type     | Default   | Form     | Effect                                                                    |
|-------|---------------|----------|-----------|----------|---------------------------------------------------------------------------|
| `-t`  | `--transport` | `Choice` | `"stdio"` | optional | Transport protocol. Choice of `stdio` and `streamable-http`, nothing else |

**Note:** `run_server()` also accepts a third value, `sse`, but the CLI `Choice` rejects it (exit code 2). Never pass
`-t sse`, and never tell a user to.

### `axvs configure` (group options)

| Short | Long                 | Type  | Default                        | Form       | Effect                                                                     |
|-------|----------------------|-------|--------------------------------|------------|----------------------------------------------------------------------------|
| `-c`  | `--camera-index`     | `int` | `None`                         | optional   | The Harvesters camera every subcommand operates on                         |
| `-b`  | `--blacklisted-node` | `str` | the library's GenICam node set | repeatable | A GenICam node excluded from read, dump, and load. Repeat per GenICam node |
|       | `--no-blacklist`     | flag  | `False`                        | flag       | Includes every writable GenICam node in read, dump, and load               |

**All three are parsed on the group**, so they must be supplied **before** the subcommand name, as in
`axvs configure -c 0 read -n Width`. Placing `-c` after the subcommand name aborts with "No such option". The option
carries no usable default, so omitting it raises a Click usage error naming the omission when the subcommand runs. It
cannot be marked required on the group without also blocking `axvs configure SUBCOMMAND --help`.

`-b` and `--no-blacklist` are mutually exclusive, and supplying both raises a Click usage error. Because `-b` carries a
non-empty default, the CLI settles the conflict by consulting Click's parameter source, so the error fires only when the
user actually named a GenICam node.

A `-c` value naming no discovered camera also raises a Click usage error, on all four subcommands. The message names the
requested index and the number of cameras the configured Producer discovers, so a count of zero points at the Producer.

### `axvs configure` subcommands

| Command | Short | Long            | Type   | Default    | Form     | Effect                                                                  |
|---------|-------|-----------------|--------|------------|----------|-------------------------------------------------------------------------|
| `read`  | `-n`  | `--node-name`   | `str`  | `""`       | optional | The GenICam node to read. When empty, lists every writable GenICam node |
| `write` | `-n`  | `--node-name`   | `str`  | (required) | required | The GenICam node to write. Written even when the blacklist names it     |
| `write` | `-v`  | `--value`       | `str`  | (required) | required | The value, coerced to the GenICam node's own type                       |
| `dump`  | `-o`  | `--output-file` | `Path` | (required) | required | The YAML file to write. Need not exist                                  |
| `load`  | `-f`  | `--config-file` | `Path` | (required) | required | The YAML file to apply. Must exist and be readable                      |
| `load`  |       | `--strict`      | flag   | `False`    | flag     | Aborts on a camera model or serial mismatch instead of warning          |

**Note:** `-f` expands to `--file-path` on `axvs cti set`, to `--frame-rate` on `axvs run`, and to `--config-file` on
`axvs configure load`. The long forms are not interchangeable, so quote the long form for any of the three.

---

## Command behavior and failure modes

### How a failure reaches the user

Every one of the eleven leaf commands wraps its body in a decorator that catches whatever the body raises, reports it
through the console at the ERROR level, and returns normally. The command therefore exits 0 on a body failure, and the
user sees a single formatted ERROR line. The console writes to the standard error stream, so a user capturing standard
output alone sees nothing. Read the message text to identify the fault, and never ask a user for an exit status as
evidence that a command worked.

A malformed invocation is the one failure that keeps its own contract, and it aborts at exit code 2 with a usage
message wherever it is detected. That covers Click's own parameter validation, which runs before the body and rejects
a missing required option, an unparseable value, and a `click.Path` constraint. It also covers a usage error raised
inside a command body, such as the `axvs configure` camera index checks, because the decorator lets a Click exception
pass through, and one raised in the `axvs configure` group callback, such as `-b` arriving together with
`--no-blacklist`, which aborts before any subcommand runs.

The exception each failure mode names below is the one the body raises, and it identifies the fault even though the
user never sees the class name printed.

### `axvs configure write`

Echoes `Node '{name}' written with {value}. The camera reports {observed} for it on this connection.` The command reads
the node back over the connection it wrote on, because a node that advertises ReadWrite access can still round the write
to its step increment or reject it. Which of the two a camera does is camera-specific, so a value violating the
increment aborts with an error on one camera and lands rounded on another. A reported value differing from the requested
one is therefore the value in force.

Each subcommand opens and closes its own connection, so a camera that discards node state across a device close serves
its previous values to the next command. See `/camera-setup` for the UserSet route a setting takes when it has to
survive.

### `axvs cti set` and `axvs cti check`

`set` persists the Producer path for every later runtime and echoes `AXVS CTI file: Set to {path}.` on success.

`check` prints one of two lines.

| Observed                                         | Meaning                                                  |
|--------------------------------------------------|----------------------------------------------------------|
| `AXVS CTI file: Configured and valid. Path: ...` | A Producer is set and loads                              |
| `AXVS CTI file: Not configured or invalid. ...`  | No Producer is set, or the configured path fails to load |

The `AXVS_CTI_PATH` environment variable supplies the path for a single runtime and takes precedence over the persisted
one, so a host reporting a Producer nobody configured has that variable set.

### `axvs check devices`

Probes OpenCV indices and enumerates GenTL devices, then prints each interface's cameras under its own heading. The line
format differs from `list_cameras_tool`, which returns the compact `OpenCV #0: 1920x1080@30fps` form. The CLI prints
`OpenCV camera 1: index=0, frame_height=..., frame_width=..., frame_rate=...` and numbers its lines from 1, so never
read the leading number as a camera index. Read `index=` instead.

| Condition              | Behavior                                                                                      |
|------------------------|-----------------------------------------------------------------------------------------------|
| No OpenCV cameras      | Prints a warning line. Not an error                                                           |
| OpenCV cameras present | Warns first that OpenCV resolves no model or serial, and recommends `axvs run` to map indices |
| No Harvesters cameras  | Prints a warning line. Not an error                                                           |
| No CTI file configured | Prints that same warning line with no note naming the cause. Ask for `axvs cti check` first   |

### `axvs check compatibility`

Reports one of three states and never raises. `Not met.` means FFMPEG is absent, and the GPU is not evaluated at all in
that branch. `Partially met.` means FFMPEG resolved but no NVIDIA GPU answered `nvidia-smi`. `Fully met.` means both.

### `axvs run`

Builds a DataLogger and one VideoSystem, then drives them from an interactive keypress loop. `q` terminates, `w` starts
frame saving, and `s` stops it. Every other key prints a warning and re-prompts.

The session's parameters are **fixed in the command**, and no option exposes them. This is the third parameter set in
the plugin, alongside the MCP session defaults in `/camera-setup` and the code defaults in `/camera-interface`.

| Fixed value                       | Consequence                                                                            |
|-----------------------------------|----------------------------------------------------------------------------------------|
| `system_id=111`                   | The archive is `111_log.npz` and the video is `111.mp4`                                |
| `name="live_camera"`              | The manifest entry is registered under that name                                       |
| `instance_name="axvs_live_run"`   | The log directory is `axvs_live_run_data_log/`, not the MCP session's                  |
| `display_frame_rate=25`           | A preview opens on every platform except macOS, and any `-f` below 25 aborts the start |
| `H264`, `FAST`, `YUV420`, `QP 15` | Compatibility-first encoding. Not the production set `/camera-interface` gives         |

The display rate may not exceed the camera's acquisition rate, and that bound is validated on every platform, so
`axvs run -f 15` raises `ValueError` during VideoSystem construction before the session starts. Hand a user a `-f`
value of 25 or above, or expect the command to abort.

Archive assembly runs in a `finally` block, so an ordinary interrupt still assembles. Only a killed process leaves raw
`.npy` entries behind, and `/post-recording` owns the manual recovery.

**On termination the system may stay alive for up to 600 seconds** draining buffered frames. A user reporting a hung
`axvs run` shortly after pressing `q` is describing normal behavior.

### `axvs process`

Runs one recording's jobs **sequentially in a plain loop**.

| Condition                                  | Behavior                                                                             |
|--------------------------------------------|--------------------------------------------------------------------------------------|
| No `camera_manifest.yaml` under `-ld`      | `FileNotFoundError` naming the log directory and the absent manifest                 |
| Several manifests under `-ld`              | `ValueError`. Pass each DataLogger output directory on its own invocation            |
| Manifest registers no source               | `ValueError`                                                                         |
| A requested source or job ID unregistered  | `ValueError`                                                                         |
| A source's archive absent or ambiguous     | `FileNotFoundError`                                                                  |
| An archive resolves but cannot be read     | `FileNotFoundError` from the `-w -1` width resolution, before that job starts        |
| Resolved archives span several directories | `ValueError` naming the one-directory-per-invocation rule                            |
| A job raises mid-run                       | The tracker marks that job FAILED, the error is reported, and later jobs never start |

That last row is the divergence that matters most. The MCP batch isolates a failure to its own job and carries the rest
of the batch through, while the CLI abandons the remaining jobs at SCHEDULED. A user reporting "it stopped partway" has
hit a failure, not a cancellation.

**Note on tracker contention:** both paths lock the same `camera_processing_tracker.yaml` through its `.lock` file, on
the CLI side when the pipeline aligns the tracker and again on every job state transition. A user running `axvs process`
against a directory the agent is preparing or executing makes whichever side asks second raise a `TimeoutError`. Ask the
user to stop their CLI run before preparing or executing that directory, and never start an MCP batch over a directory
the user has a run in.

---

## Fallback: what to tell a user when MCP is unavailable

Confirm the server is genuinely unrecoverable through `/video-mcp-environment-setup` before handing any of these over.

| Blocked MCP tool                                                         | Tell the user to run                                   |
|--------------------------------------------------------------------------|--------------------------------------------------------|
| `set_cti_file_tool`                                                      | `axvs cti set -f <cti>`                                |
| `get_cti_status_tool`                                                    | `axvs cti check`                                       |
| `list_cameras_tool`                                                      | `axvs check devices`                                   |
| `check_runtime_requirements_tool`                                        | `axvs check compatibility`                             |
| `read_genicam_node_tool`                                                 | `axvs configure -c <index> read -n <node>`             |
| `write_genicam_node_tool`                                                | `axvs configure -c <index> write -n <node> -v <value>` |
| `dump_genicam_config_tool`                                               | `axvs configure -c <index> dump -o <yaml>`             |
| `load_genicam_config_tool`                                               | `axvs configure -c <index> load -f <yaml>`             |
| The four session tools                                                   | `axvs run -i <interface> -c <index> -o <dir>`          |
| `prepare_log_processing_batch_tool` + `execute_log_processing_jobs_tool` | `axvs process -ld <logs> -od <out>`                    |

Three caveats. `axvs run` records at fixed compatibility encoding, so it substitutes for a session test and never for
a production recording. `axvs process` carries the single-directory and abort-on-first-failure limits its own section
above states. Neither `axvs` command reports its results back in a machine-readable form, so ask the user to paste the
terminal output.

Everything else genuinely blocks until the server is back: camera manifest read and write, archive assembly, video file
validation, camera data discovery, every batch status, timing, cancel, reset, and cleanup tool, and frame statistics
analysis. Say so plainly.

---

## Related skills

| Skill                          | Relationship                                                                         |
|--------------------------------|--------------------------------------------------------------------------------------|
| `/camera-setup`                | Owns the session, GenICam, and manifest tools behind `axvs run` and `axvs configure` |
| `/log-processing`              | Owns the MCP batch workflow and the authoritative job sizing model                   |
| `/video-mcp-environment-setup` | Owns the `--help` exemption, the `axvs mcp` transports, and MCP recovery             |
| `/camera-interface`            | Context: the production VideoSystem code no `axvs` command replaces                  |
| `/post-recording`              | Downstream: recovers an `axvs run` session whose process was killed before assembly  |
| `/log-input-format`            | Reference: the assembled archives `axvs process` reads under `-ld`                   |
| `/log-processing-results`      | Downstream: the feather output both paths write                                      |
| `/pipeline`                    | Context: where each CLI command sits in the end-to-end pipeline                      |

---

## Verification checklist

```text
Answering a CLI question, tool-settled (run `axvs COMMAND --help`, the sole sanctioned invocation):
- [ ] Answered from this skill or from `axvs COMMAND --help`, never from memory
- [ ] Quoted the long option form, and never presented `-h` as a help alias

Answering a CLI question, reader-judged:
- [ ] Named the MCP equivalent alongside any command the agent could have run itself
- [ ] Invoked no `axvs` command other than `--help`

Handing a user a CLI command, reader-judged:
- [ ] Confirmed MCP is genuinely unavailable via `/video-mcp-environment-setup` first
- [ ] Printed the command for the user instead of running it
- [ ] Named `-i opencv` or `-i harvesters` explicitly on any `axvs run` command, since the default is `mock`
- [ ] Warned about the abort-on-first-failure loop before recommending `axvs process`
- [ ] Confirmed no MCP batch is holding the tracker for that output directory
```

Versions

RepositoryScoreLicence
This page · Sun-Lab-NBB/ataraxis100Apache-2.0
nightgauge/nightgauge100Apache-2.0
Sun-Lab-NBB/ataraxis100Apache-2.0
even-realities/everything-evenhub95MIT

Database snapshot: 13.11.2026 · package version 1878f8f123ad (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100video-mcp-environment-setup
    Diagnoses and resolves ataraxis-video-system MCP server connectivity issues. Covers environment verification, command availability, Python version checks, dependency validation, and conda/pip/uv environment configuration. Use when the axvs (video-system) MCP tools are…
  • 100create-cli
    This skill should be used when the user asks to "design a CLI", "create command-line interface", "design CLI parameters", "plan CLI UX", or needs help structuring command-line tool interfaces with proper arguments, flags, subcommands, and user experience patterns.
  • 96add-command
    Add a subcommand to this Rust CLI with its handler, errors, output and tests. Use when the user asks for a new command, subcommand or option that does work.
  • 86add-command
    Add a command or command group to this Typer CLI with its settings, errors, output and tests. Use when the user asks for a new subcommand, option or setting.
  • 100add-cli-option
    Add a new Remotion CLI or config option by creating an AnyRemotionOption, registering CLI parsing, wiring config setters, and updating documentation. Use when adding or converting command-line flags or Remotion options.
  • 100add-config-option
    Use when a ticket adds or changes a configuration option — an environment variable, a settings key, a CLI flag, a YAML field — that operators set, and it must have one source of truth, a validated default, precedence rules, and documentation that cannot drift. Invoke for "make X…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.