majordomus commands
Every command this repository offers, from whichever program offers it: the graph, one command, where each one is projected, and the workflow bridge derived from it
majordomus commands
Usage
majordomus commands [OPTIONS] [COMMAND]Commands
- majordomus commands list Every command, one line each: what it is, what running it changes, and where it is projected
- majordomus commands show One command in full: its arguments, its effect, what it needs, and every surface that carries it
- majordomus commands explain Why one command appears where it does: the declaration it came from, the policy that placed it, and the reason for every surface that withholds it
- majordomus commands graph The whole graph as one document, with its fingerprint and every diagnostic
- majordomus commands bridge Materialise the workflow bridge from the graph, and refresh the cache the completion reads; writes nothing when the graph has not changed
Arguments
| argument | value | default | description |
|---|---|---|---|
| --repo | <PATH> | — | Start the search for the repository root here (default: the current directory) (accepted by every subcommand) |
| --discovery | vcs | filesystem | vcs | How declarative files are enumerated (accepted by every subcommand)
|
| --strict | flag | — | Refuse to proceed when any file of the layer carries an error diagnostic (accepted by every subcommand) |
| --share | <DIR> | — | The tool distribution's share directory (kinds.yaml, schemas/); default: $MAJORDOMUS_SHARE, then the repository's own share/, then the one beside the executable (accepted by every subcommand) |
| --format | text | json | text | Output shape (accepted by every subcommand)
|
Examples
-
Every command this repository offers
The command graph, composed from the three declarations that already exist: the clap tree of this executable, the shipped command registry of the shell tool, and the recipes the workflow runner describes. One line per command, with the program that runs it and what running it changes.
$ majordomus commandsVerified by the example tests: exits 0; prints commands, executable, read-only.
Where this comes from
Declared once in apps/majordomus-cli/src/cli.rs: clap for the structure, typed Rust metadata beside it for the examples. This page, majordomus commands --help, docs/generated/cli.md and docs/generated/cli.json are projections of that one declaration.
The whole command line on one page: the registry's command-line page. The task lifecycle (init, start, finish, doctor, ...) belongs to the shell tool, a different program: Commands and its specification.