Skip to main content

ovecc conventions

Learns the dominant conventions from the repository itself — naming roles, dependency directions, database access patterns — and reports the files deviating from them. No rulebook to write: the codebase is the rulebook.

Usage: ovecc conventions [OPTIONS]

Example​

$ ovecc conventions
Detected conventions:
  (none with sufficient evidence)

On a small or young repository this is the expected output: conventions is silent below its evidence thresholds by design. A convention only exists when enough of the codebase agrees on it; reporting "conventions" learned from three files would be noise. On larger codebases, learned conventions come with a confidence score and the deviating files.

Options​

The global options only.

  • Governance rules — declare conventions explicitly instead of learning them
  • diagnose — principle-based (not learned) smells