Reference
The exhaustive pages. Look things up here; understand them onConcepts .
CLIanalyze and config: arguments, flags, deterministic mode, and --verbose output.ConfigurationHow the five layers combine, the env-var form, LLM backends, and every key.
Two things worth knowing before you look anything up
Unknown config keys are an error. The schema isextra="forbid", so a typo fails loudly at load rather than being silently ignored. Every release also ships ci-doctor.schema.json, generated from the same pydantic model that does the validating — point your editor at it and typos never reach a commit.
Ask, don't guess. Config surprises are almost always a layer you forgot was applied. ci-doctor config --diff shows only what your file, environment and flags changed relative to the shipped defaults.
Looking for the shipped matcher packs? They are a generated catalogue onMatchers , next to the explanation of how a pack is shaped.