How Commit Doctor works

It reads a repository’s full history, links every bug fix back to the commit that caused it, and scores each commit for defect risk.

Pipeline

Hover a stage to see what it does

Long steps checkpoint as they run, so an interrupted analysis resumes instead of restarting.

What it measures

Defect risk

  • Corrective-commit detection
  • Bug-introducing commits
  • Defect density per file
  • Per-commit risk score
  • Risk drivers, with p-values

Code quality

  • Cyclomatic + cognitive complexity
  • Maintainability index
  • Nesting, long methods, long params
  • Hotspots: complexity × churn
  • Duplication, test-to-code ratio

History & people

  • Kamei change metrics
  • File ownership, minor contributors
  • Bus factor
  • Logical coupling
  • AI authorship

Debt & trend

  • Self-admitted technical debt
  • History snapshot per analysis
  • Percentile vs. other repositories