Presets

Presets are named analysis profiles that select a fixed set of metrics and defaults. They let you switch between “quick check,” “CI gate,” “risk audit,” and “full” without editing a long metric list.

What a Preset Does

Selects metrics — Replaces the config’s metrics list at run time with the preset’s list (e.g. quick → SCC + L1 overview; full → all 50+ metrics).
Does not define policy — You still configure invariants in policy.invariants; presets only control which metrics run and thus which metric keys exist for policy.

Available Presets

Preset	Typical use	Speed
quick	Dev loop, pre-commit	Very fast (1–5 s)
ci	CI/CD gates	Fast (10–30 s)
risk	Tech debt, refactor planning	Medium (30–60 s)
coupling	Dependency analysis	Medium
security	Security review	Medium
runtime	Operational analysis (needs telemetry)	Medium
ai	AI/LLM apps	Medium
full	Full audit	Slow (2–5 min)

Using Presets

CLI:

arxo analyze --preset quick
arxo analyze --preset ci --fail-fast

Config:

metric_preset: ci   # or quick, risk, full, etc.
policy:
  invariants:
    - metric: scc.max_cycle_size
      op: "=="
      value: 0

Presets vs Custom Metrics

Preset — Choose a name; metrics are fixed for that preset.
Custom config — List metrics explicitly in YAML (and optionally use a preset as a base in separate configs). You cannot add metrics into a preset from config; you can only override the whole run with a different preset or a full metrics list.

For “preset plus a few more metrics,” use a config file that lists all desired metrics (e.g. copy the preset’s list and append), or run with a preset for one use and a custom list for another.

Learn More

Presets Guide — Full list, comparison table, and examples
Metrics Overview — What each metric category provides
Configuration — metric_preset and metrics