okulo

Find where technical debt is actually costing you time.

A CLI that crosses Git history, code complexity, and authorship to surface hotspots, coupling, knowledge risk, and a refactor plan — before the interest compounds.

Install

curl -fsSL https://getokulo.dev/install.sh | sh

macOS & Linux. Windows: PowerShell one-liner. Then run okulo --help.

Read the docs See commands

okulo · hotspots

$ okulo hotspots -w 6m
window 6m · 1842 commits · 96 authors

score  revs  health  file
 92.4   48    3.1   src/billing/invoice.py  ●
 71.2   31    4.8   web/checkout/Cart.tsx   ●
 58.0   22    6.2   server/orders/api.go
 41.5   14    7.4   lib/auth/session.ts

top 10% holds 47% of recent change

What Okulo answers

Static analysis sees structure. Okulo adds change and people — so you prioritize the debt that is collecting interest.

Hotspots

Complex code that also changes often. That is where cleanup pays back.

Temporal coupling

Files that move together without an explicit dependency — hidden architecture.

Knowledge risk

Ownership islands, bus factor, and coordination pressure across components.

Commands

Run any command in a Git repo (or pass a path). Full reference in the docs.

okulo hotspotsChange frequency × complexity

okulo debtActive vs inactive debt, hours lost

okulo refactorFunction-level refactor plan

okulo couplingFiles that change together

okulo ownershipWho knows each file

okulo busfactorHow many exits the team can survive

okulo checkPR / staged quality gate

okulo mapTree map in the terminal or HTML

okulo analyzeEverything in one report (JSON-friendly)

okulo mcpMCP server for coding agents

Examples, flags, and a full team workflow → Commands documentation.

Windows

PowerShell (current user PATH is updated automatically):

irm https://getokulo.dev/install.ps1 | iex