Aliases

Type less at the terminal. The revenexx CLI resolves both built-in abbreviations (revenexx p ls → products list) and your own git-style aliases before running a command, persisted across sessions.

The CLI resolves short forms before it runs a command — git-style — so you can type revenexx p ls and get revenexx products list. There are two layers: built-in abbreviations for common services and verbs, and user-defined aliases you create with alias set.

A real command always wins over an alias of the same name, so an alias can never silently shadow core functionality. Built-in service aliases are also gated on the service actually existing in your tenant's API, so an abbreviation for a service you don't have is simply ignored rather than resolving to the wrong thing.

Built-in abbreviations

Two kinds are recognised, resolved left to right: the first token can be a service abbreviation, the second a verb abbreviation.

KindExamples
Services (first token)p/prod → products, o/ord → orders, cust → customers, cat → categories, inv → inventories, pay → payments, ship → shipping, msg → messaging, cart → carts, price → prices
Verbs (second token)ls/l → list, g → get, mk/new/add → create, up/upd/edit → update, rm/del/d → delete

So all of these resolve to products list:

Shell
revenexx products list
revenexx p list
revenexx p ls

See the full built-in table at any time with:

Shell
revenexx alias list

User-defined aliases

Create your own shortcuts for the commands you run most. They're stored in your global config (~/.revenexx/prefs.json) and shared across every session on the machine.

Set an alias — quote multi-word expansions:

Shell
revenexx alias set deploy "apps create-deployment --activate true"

Now revenexx deploy runs the full command. You can pass extra arguments after the alias and they're appended to the expansion:

Shell
revenexx deploy --app-id app_123
# → apps create-deployment --activate true --app-id app_123

List every alias (yours and the built-ins) and remove one you no longer need:

Shell
revenexx alias list
revenexx alias remove deploy

If you pick a name that matches a built-in command, the CLI warns you when you set it — the command wins, so the alias would never resolve.

How resolution works

When you run a command, the CLI rewrites the arguments in this order, before anything else runs:

  1. User-defined alias on the first token — expanded into its stored command line (unless a real command already has that name).
  2. Built-in service abbreviation on the first token — mapped to the canonical service, if that service exists.
  3. Built-in verb abbreviation on the second token — mapped to the canonical verb, scoped to the resolved service's commands.

Everything downstream — interactive prompts, the safety banner, --help, --json — sees the fully resolved command, so aliases behave exactly like typing the long form.

What's next

Was this page helpful?