Command

okulo hotspots

Rank files by change frequency × complexity — where cleanup usually pays back.

coreprioritization

When to use it

Start of a health pass, sprint planning, or before picking refactor targets.

Usage

okulo hotspots [repo] [options]

Options

OptionDefaultDescription
-w, --window12mHistory window for change frequency
--top-percent10Share of the ranking marked as hotspots (●)
--components A,BallLimit ranking to named components
-n, --limit20Rows to display
-f, --formattabletable or json

Examples

Last six months, top 15 files

okulo hotspots -w 6m -n 15

Backend-only in a monorepo

okulo components
okulo hotspots --components backend -w 6m

Stricter hotspot cut + JSON export

okulo hotspots --top-percent 5 -f json -o hotspots.json

Sample output

Illustrative terminal output (column layout matches the real CLI):

Hotspots  change frequency × complexity
#  file                          score  revs  churn  loc  cognitive  authors  health
─  ────────────────────────────  ─────  ────  ─────  ───  ─────────  ───────  ──────
1  ● src/billing/invoice.py       92.4    48   6120  840        210        6     3.1
2  ● web/checkout/Cart.tsx        71.2    31   4044  520        145        4     4.8
3    server/orders/api.go         58.0    22   2102  310         88        5     6.2
4    lib/auth/session.ts          41.5    14    980  190         42        3     7.4

4 hotspot(s) = top 10% of 120 files · 8% of the code · 47% of all changes · 51% of churn

How to read it

Tips

Related