Docs/Scripts

Shortcuts

Shortcuts are defined in .shortcuts.yaml and allow you to create aliases for your scripts. For example:

shortcuts:
  b: build.yaml
  t: test.yaml
  cm: commit.yaml

Run zirv b instead of zirv build.yaml. This will execute the build.yaml script.

A shortcut key that collides with a reserved command name (for example c, already create's alias) can never be reached; zirv help marks it as shadowed in the listing.

Reserved Command Names#

help, version, init, create, ctx, memory, context, setup, report, chat, agent, skill, workflow, test, verify, artifact, frontend, commands, update, session, tour, native, benchmark, and their short aliases h, v, i, c,

are handled as built-in commands before zirv ever looks in .zirv/. The comparison is case-insensitive (Chat/CHAT collide just as much as chat, matching how NTFS/APFS resolve script filenames), so a differently-cased script or shortcut is caught too, even though only the exact lowercase spelling is literally intercepted as a routing alias. A script file or shortcut key using one of these names (in any case) can never be invoked:

• zirv help lists it but marks it (shadowed by a built-in command, unreachable).
• zirv create warns about the collision and asks for confirmation before creating it anyway; in non-interactive mode (see Creating a New Script) the collision is an error instead.