Conventions

Your codebase has years of implicit decisions baked in. Now they're visible.

Octokraft reads your actual code and extracts the patterns your team already follows across 6 categories: naming, error handling, structure, API design, documentation, and imports. No config files to maintain. No stale style guides to dig through.

Conventions overview showing overall consistency score and convention cards with conformance bars

Real code, not abstract rules

Every convention links back to actual files in your repo. Conforming files show up in green, deviating files in orange. You see file paths and code snippets right there, so you can verify a pattern without switching context.

  • Green examples show how your team actually writes this pattern today, pulled straight from your repo
  • Orange examples show the exact lines where a file breaks from the convention and why
  • Snippets are inline. You understand what's different in seconds without opening your editor
Expanded convention card showing conforming and deviating code examples with file paths and snippets

See exactly how consistent your codebase actually is

Each convention gets a conformance rate: how many applicable files follow it vs. how many don't. Grouped across 6 categories so you know exactly where consistency is strong and where quality is drifting.

  • Per-convention conformance rate tells you the actual ratio of files that follow vs. deviate
  • 6 categories (Naming, Error Handling, Structure, API Design, Documentation, Imports) so you can jump to what matters
  • One overall consistency score you can track sprint over sprint to see if things are getting better or worse
Multiple convention cards showing different conformance levels grouped by category

You decide what gets enforced

Not every detected pattern is worth enforcing. Confirm the ones your team cares about, dismiss the rest, and watch consistency over time.

Confirm

Lock in a convention as intentional. From now on, deviations get flagged in PRs and health assessments.

Dismiss

Mark a pattern as noise. It drops out of reports and stops affecting your consistency score.

Track drift

See conformance rates move up or down across assessments as your team tightens or relaxes conventions.

Catch convention drift in the PR, not six months later

When someone opens a pull request that breaks a confirmed convention, Octokraft flags it right there in the PR analysis. Before merge. Before it becomes the new normal.

  • Every PR is checked against all confirmed conventions automatically
  • Violations show the expected pattern side-by-side with the code that was actually introduced
  • You catch inconsistencies during review instead of finding them buried in the next health assessment
Convention drift panel in PR analysis showing violations with expected vs actual patterns

Stop letting consistency drift

Detect conventions from your actual code. Enforce the ones that matter. Catch drift on every PR.

Try Octokraft