ovecc diagnose
Named architectural smells at component granularity — evidence, the principle broken, confidence, and a curated remediation.
ovecc advise
Everything touching one file, module, or component — each finding with its established fix. Call before editing.
ovecc metrics
Per-component Martin metrics — fan-in/out, coupling, instability, abstractness, distance from the main sequence, churn.
ovecc explain
A deterministic, offline explanation of any element's role — every sentence backed by a fact.
ovecc impact
Blast radius of changing a module, symbol, API, or table — impacted nodes, the paths that reach them, and a risk score.
ovecc query
Structured graph queries — deps, rdeps, paths, cycles, reachability, hotspots, and element search.
ovecc export
Export a context slice for one element, or the whole dependency graph — as JSON or a self-contained offline HTML viewer.
ovecc hotspots
The technical-debt ranking — churn × coupling × ownership fragmentation × violations, normalized 0–100.
ovecc conventions
Conventions learned from the repository itself — naming roles, dependency directions, DB access patterns — and the files deviating from them.
ovecc components
Subsystems recovered from the dependency graph by ACDC dominance clustering — a second view beside the directory-derived modules, and where the two disagree.
ovecc coupling
The file pairs your history keeps changing together — evolutionary coupling with Jaccard, lift, directed confidence, and witness commits.
ovecc selfcheck
Turn the tool on itself — for each rule, does the code it flags actually get corrected more often than the rest of the repository?