Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

majordomus why diagnose

What the symptoms you recognise imply: the areas they weigh towards and the mechanisms that answer them

What it is

read only

What the symptoms you recognise imply: the areas they weigh towards and the mechanisms that answer them

Identity
executable.why.diagnose
Program
executable
Runs
non interactive
Requires
repositorylayer

Where it appears

Command line
majordomus why diagnose
Workflow
just why-diagnose
MCP tool
majordomus_why_diagnose
HTTP
/api/v1/why/diagnose
Declared in
apps/majordomus-cli/src/cli.rs
Capability
why.diagnose

Arguments

argumentvalues fromrequiredhelp
--signal—A signal id or a moment id; repeat for each one you recognise. Without any, the questionnaire is printed
--repo—Start the search for the repository root here (default: the current directory)
--discovery—How declarative files are enumerated
--strict—Refuse to proceed when any file of the layer carries an error diagnostic
--share—The tool distribution's share directory (kinds.yaml, schemas/); default: $MAJORDOMUS_SHARE, then the repository's own share/, then the one beside the executable
--format—Output shape
--audience—Only moments this audience recognises
--area—Only moments in this operational area
--tag—Only moments carrying this tag
--severity—Only moments of this severity
--frequency—Only moments of this frequency
--lifecycle—Only moments at this stage of work
--capability—Only moments naming this capability of the executable
--names-command—Only moments naming this command
--featured—Only the moments the homepage features
--all—Include drafts and deprecated moments, not only the public ones
--query—Case-insensitive text over identities, titles, hooks, summaries, tags, aliases, signals, examples and bodies