How many of the spec's requirements were verified for this tool.
See /coverage for the full matrix.
Level
Total
Verified
Unverified
MUST
28
19
9
SHOULD
21
13
8
MAY
10
10
0
Top Issues
FAILError messages include a hint or remediation phraseFail-Fast, Actionable Errorsstderr lacks a hint phrase. Looked for one of: try , use , expected , did you mean, see , run , for more, tip:, help:, hint:, suggestion:, available . Error messages must name what to do next, not just the symptom.
WARN--json / --jsonl short aliases for --outputStructured, Parseable Outputno --json or --jsonl short alias found. Agents and pipelines benefit from short forms alongside the canonical `--output` enum.
target satisfies P1 via alternative gate (help-on-bare or stdin-primary)
SKIP
Flags advertise env-var bindings in --help
target exposes no flags in --help
PASS
Secret-bearing flags expose stdin or *-file companion
PASS
`--help` advertises default values for flags
WARN
Rich-TUI affordance for TTY contexts
no rich-TUI affordance detected (no `--tui`/`--interactive`/`--ui` flag, no spinner/progress/tui mention in --help). MAY-tier — rich TUI in TTY contexts is a nice-to-have, not required.
no --output/--format flag detected — tool does not ship structured output. Schema-discovery requirements (p2-must-schema-print, p2-should-schema-file) collapse to n/a via antecedent propagation.
N/A
Structured-output CLI exposes its schema at runtime
antecedent `p2-json-output` is opt_out: no --output/--format flag detected — tool does not ship structured output. Schema-discovery requirements (p2-must-schema-print, p2-should-schema-file) collapse to n/a via antecedent propagation.
WARN
--json / --jsonl short aliases for --output
no --json or --jsonl short alias found. Agents and pipelines benefit from short forms alongside the canonical `--output` enum.
WARN
`--raw` flag for pipe-safe unformatted output
no `--raw` flag advertised. MAY-tier — useful for pipelines that want to strip formatting before piping to other tools.
no `--output` or `--format` flag advertised; vacuous skip for MAY-tier extra formats.
WARN
Bad invocation exits with structured usage-error code (2)
bad invocation exited with code 1. The 0/1/2/77/78 convention reserves code 2 for usage errors; using a different non-zero code (often 1) blurs the distinction between usage errors and general failure.
SKIP
Errors emit JSON envelope with `error`/`kind`/`message` under `--output json`
binary does not advertise `--output json` in --help; MUST applies only to CLIs that opt into the JSON contract.
SKIP
JSON success and error envelopes share their non-payload key set
binary does not advertise `--output json` in --help; envelope-consistency only applies to CLIs that opt into the JSON contract.
`examples` subcommand or `--examples` flag for curated usage patterns
no `examples` subcommand or `--examples` flag found. MAY-tier — a curated usage block keeps agents from hunting through long help text.
WARN
Short `-h` summary differs from `--help` long form
`-h` and `--help` produce byte-identical output. SHOULD-tier — clap renders the short summary on `-h` and the full description on `--help` when `long_about` is set; collapsing them gives agents no concise list-level grep target.
SKIP
Each subcommand's `--help` ships at least one invocation example
binary has no subcommands; MUST applies conditionally to CLIs that use them.
WARN
Help text pairs human and `--output json` example invocations
no paired text + `--output json` example found within 5 lines in top-level or any subcommand `--help`. Pairing keeps agents from reverse-engineering the JSON invocation from the text one.
Error messages include a hint or remediation phrase
stderr lacks a hint phrase. Looked for one of: try , use , expected , did you mean, see , run , for more, tip:, help:, hint:, suggestion:, available . Error messages must name what to do next, not just the symptom.
SKIP
`--output json` produces JSON-formatted errors
binary does not advertise `--output json` in --help; SHOULD applies only to CLIs that opt into the JSON contract.
no `--verbose` / `-v` flag advertised. SHOULD-tier — agents debugging failures need a way to escalate diagnostic detail.
SKIP
`--limit` / `--max-results` flag for list operations
no list-style subcommand detected (list/ls/search/query/find/show/get); vacuous skip for the list-only SHOULD.
SKIP
Cursor-based pagination flags for list traversal
no list-style subcommand detected; vacuous skip for the list-only MAY.
SKIP
`--timeout` flag for long-running operations
no long-running subcommand detected (serve/daemon/watch/tail/monitor/follow/run/start/stream); vacuous skip for the conditional SHOULD.
WARN
Help text advertises TTY-aware verbosity behavior
no TTY-aware language found in `--help`. MAY-tier — automatic verbosity reduction when stdout is piped or redirected lets agents skip the explicit `--quiet` flag. Behavioral probes cannot simulate a real TTY without a pty crate, so this audit relies on documented intent.
