git:20261012.455f96e to git:20261014.50f278d

7 added, 0 removed. Audit A to A.

---

name: crew-approve

description: Approve the commit or push Claude just showed you (auto and dontAsk modes).

argument-hint: "[commit | push | commit+push] (nothing: what was just refused)"

disable-model-invocation: true

metadata:

kind: command

---

# /crew-approve

Argument: $ARGUMENTS

The user typed this command. Typing it is the approval: `hooks/prompt-approval.sh` read the message itself and

recorded it, tied to what is staged, to `HEAD` and to this session, for 30 minutes or until the user's next

message. Nothing in this text records anything, and you cannot give this approval for the user.

Read the line Crewforth added to this turn and do what it says:

- **"approval recorded"**: run exactly what it names, each command alone in its call. A commit is

`git commit -m '…'` with the message you showed (single-quoted, or from a here-document with a quoted delimiter);

a push is `git push <remote> <branch>`. The review record of §4.6 is still required.

- **"approval NOT recorded"**: tell the user the reason it gives, and run nothing.

- **With no argument** the command approves what the gate last refused in this session (the line says which:

"approved: commit+push"); when nothing was refused, or it was more than 30 minutes ago, nothing is recorded and

the line says so.

- **No such line**: the session is in a mode where the gate asks the user itself (`default`, `acceptEdits`), or

the argument was not `commit`, `push` or `commit+push`. Say which, and in the first case run the command and let

the gate's own prompt ask.

+ In `auto` the same approval can be given with one click: the gate's refusal prints a fixed AskUserQuestion, and

+ the user's answer is recorded exactly like this command. Where a `PermissionRequest` hook may be wired (in the

+ user's, the project's or a plugin's settings, or in a skill's or an agent's front matter), that question is closed,

+ and so is the gate's own prompt in `default` / `acceptEdits`, because such a hook answers a prompt before the user

+ does. This command is then the one approval left, in those modes too. Settings passed with `--settings` and

+ managed settings delivered by a server cannot be read, so a hook there is past the check.

Force-push and the rest of §4.5 are not opened by this.