gz-validate
Use to check manifest, ledger, document or surface validity against schema rules.
SKILL.md.gzkit/skills/gz-validate/SKILL.md
GitHubgz validate
Overview
Run gzkit's governance validators. Each --<scope> flag is one validator, and
VALIDATOR_REGISTRY in src/gzkit/commands/validate_cmd.py is the authority
for which scopes exist and their tier; uv run gz validate --help lists the
flags and docs/user/manpages/validate.md says what each checks.
- A bare
gz validateruns every default-tier scope. This is theValidatestep ofuv run gz check. - An explicit-tier scope runs only when its flag is named.
gz checkenrolls some of them as their own steps; the rest run on no commit path (GHI #1063), so a greengz checksays nothing about them. - Flags combine, except a solo-only scope, which refuses to run with any other scope (exit 1) and must be run alone (GHI #704).
--jsonchanges the rendering, never the exit status (GHI #995).- In an open MX hangar (
gz mx), ERROR-level scopes report without failing; CRITICAL-level scopes still fail. The run says so when it demotes one.
Exit codes: 0 clean; 3 when every finding is a policy breach; 1 when any finding is an ordinary error, or on a refused combination. Each finding names the artifact, the rule it breaks and the recovery.
Workflow
- Run the scope the question needs,
uv run gz validate --<scope>, or bareuv run gz validatefor the default tier. Capture output to a file and read$?straight after it: the verifier-pipe gate refuses a piped verifier or one followed by another statement (GHI #589). - For each finding, fix the named surface as its message directs, then re-run the same scope until it exits 0.
- Report the scopes run, the exit code and each finding fixed or still open.
Example
uv run gz validate
uv run gz validate --deprecated-verb-prescription
uv run gz validate --briefs --json