CLI reference / quality / hooks / status

stado quality hooks status

Invocation

stado quality hooks status [OPTIONS]

Purpose

Read where each checkout's pre-push gate stands: installed, outdated, absent, foreign (a hook that is not Stado's), governed (by core.hooksPath), no checkout on this machine, or unreadable (Git or the hooks directory could not be read, which exits non-zero)

Required inputs and options

Input or optionContract
--product <PRODUCT>The catalogued product whose checkouts are taken: the canonical checkout of its owner repository and of every surface's and installation's repository
--allEvery catalogued product's checkouts
--jsonOne document on stdout: each checkout's repository, products, path, hooks directory, state, whether an earlier hook is chained and what the verb did

Output and state effect

This is an inspection/reporting operation. It emits the result described above and does not change managed state unless an explicit option in this page says otherwise. Pass `--json` when the command exposes that machine-readable option.

Refusals

  • Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.