Command

`okulo log`

Summarize the Git history Okulo will analyze — commits, authors, files, and date range.

orientationfast

When to use it

Run this first when numbers look wrong, after a shallow clone, or when changing -w. If log looks empty, every other command will too.

Usage

okulo log [repo] [options]

Options

Option	Default	Description
`-w, --window`	12m	History window to summarize
`-f, --format`	table	`table` or `json` (JSON dumps every commit + files)

Examples

Check the default window

okulo log
okulo log -w 6m
okulo log ~/code/my-repo -w 90d

Export full history for custom tooling

okulo log -f json -o commits.json
jq '.commits | length' commits.json

Sample output

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

Git history  window: 6m
  commits   1842
  authors   24
  files     961
  range     2025-04-10 → 2025-10-10

author           commits  share
───────────────  ───────  ─────
Ada Lovelace         412    22%
Grace Hopper         301    16%
Alan Turing          188    10%
…

How to read it

commits / authors / files — volume Okulo will use for rankings. Near-zero commits means a bad window or a shallow clone.
range — calendar span actually covered. If it ends months ago, update the clone.
share — who commits most in the window (activity, not ownership quality).

Tips

A shallow clone (git clone --depth 1) has almost no history — run git fetch --unshallow.
Prefer fixing the window here before debugging hotspots or debt.

okulo log