CLI overview
What every ivar command has in common — the machine-readable contract, colour handling, and the command groups.
The harness calls these commands for you. This section documents them for when you want to run one yourself, script one, or understand what a slash command just did.
ivar --help
ivar <group> <command> --helpCommand groups
| Group | What it owns |
|---|---|
| Hall | init, sync, status, doctor, cleanup, migrate, repo, provider |
| Feature | feature create, promote, deliver, integrate, and the rest of the feature lifecycle |
| Session | session start, connect, convert, stop, relay, prune |
| Skill | skill add, update, detach, sync, doctor |
ivar plan is also a group, driven almost entirely by
/ivar-plan rather than by hand.
--json
Every command takes it.
ivar status --jsonOne value, two renderings
--json prints exactly the value the command computed. The human-readable
text is a rendering of that same value, so the two can never tell you
different things — script against the JSON.
--color
auto (the default) follows NO_COLOR, then FORCE_COLOR, then whether the
stream is a terminal — a pipe or a redirect gets none. always and never
override all of that.
Only labels are ever coloured; values never are, so --json output is
unaffected either way.
Hall upkeep
Keeping the hall honest from inside the harness — reconciling against ivar.json, listing what is registered, and authoring the setup script a fresh worktree needs.
ivar hall
Commands that create a hall and keep a checkout in line with ivar.json — init, sync, status, doctor, repo and provider.