Repository navigation
execute
Run a stored command.
crower execute <command> [params...]crower <command> and cr <command> are the short forms. Use the explicit
execute when the name collides with a subcommand (list, create, β¦).
| Flag | Effect |
|---|---|
-l, --last
|
Run the most recently executed command |
-c, --create
|
Run the most recently created command |
-u, --update
|
Run the most recently updated command |
-n, --dry-run
|
Print the expanded line(s) and the target; run and record nothing |
crower execute deploy
cr deploy # same thing
crower execute greet John dev # {1} = John, {2} = dev
crower execute --last # re-run what you just ran
crower greet John dev --dry-run # print the expanded line β run nothingThe command is attached to your terminal: it reads the keyboard, prints as it
goes and keeps its colours. ssh, vim, htop, git rebase -i and anything
that asks a question work through crower and through a
shell alias. Ctrl+C goes to the command, not to crower,
so the command decides how to stop and crower reports how it ended.
A command with a Timeout runs in its own process group so it can be stopped
cleanly: it gets no keyboard input, and Ctrl+C cancels it.
{1}, {2}, β¦ are positional placeholders; {} takes the remaining arguments.
Every value is quoted before it reaches the shell, so a value with a space or
; stays one value.
A command with Steps gets the same substitution in every step. A step with no
placeholder is left as written, and passing parameters when no step has one is
an error rather than a silent drop.
crower create find "grep -rn {1} {2}"
cr find "TODO" "internal/" # quoted correctly, even with spacesA command can say where and how it runs. create and update set Shell,
Cwd and Timeout with --shell, --cwd and --timeout; Env (and Steps)
live in the configuration file or in a pack.
| Field | Meaning |
|---|---|
Shell |
sh, pwsh or cmd. Empty keeps the platform's own shell. |
Cwd |
Working directory; a leading ~ is the user's home. |
Env |
Entries merged over the process environment. |
Timeout |
A Go duration (120s, 2m) applied to each step. |
An Env value that is exactly ${VAR} reads the process environment; an unset
variable is an error rather than an empty value. A literal under a
secret-looking key (*TOKEN*, *SECRET*, *PASSWORD*, *_KEY, β¦) is refused,
because a shared pack carries placeholders, never secrets. An unknown shell, a
missing folder, a bad duration, or a secret literal fails before anything runs.
Every step of a Steps command inherits the whole target.
[deploy]
Description = "Ship the API"
Exec = "rsync -az ./ {1}:/srv/api && ssh {1} 'systemctl restart api'"
Shell = "sh"
Cwd = "~/projects/api"
Env = { STAGE = "prod", TOKEN = "${DEPLOY_TOKEN}" }
Timeout = "120s"
Params = ["host"]
AllAlias = ["d"]Β© 2025 Felipe Inoue Β· crower is MIT licensed Β· third-party notices