Command

`okulo people`

Per-person churn, knowledge share, and impact if they become inactive.

teamimpact

When to use it

Planning coverage, reviewing inactive contributors, or combining with [teams] in config.

Usage

okulo people [repo] [options]

Options

Option	Default	Description
`--inactive-after`	6m	No commits in this period ⇒ treated as gone
`--source`	blame	`blame` or `churn`
`--components A,B`	all	Only count work touching these components

Examples

Team snapshot

okulo people
okulo people --inactive-after 3m

Platform team surface area

okulo people --components backend,infra

Sample output

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

People  window activity · knowledge held · impact if they left
author           team      status  commits  churn   owns  main of  islands  hotspots  files at risk
───────────────  ────────  ──────  ───────  ─────  ─────  ───────  ───────  ────────  ─────────────
Ada Lovelace     Platform  active      412  88k   28.0%      140       11         4             96
Grace Hopper     Product   active      301  61k   19.0%       90        6         2             54
Old Contractor   -         gone         44  12k    6.0%       22        5         0             22

How to read it

owns / main of / islands — knowledge footprint (from blame/churn), not “value ranking”.
hotspots — hotspot files where they are the main author: critical for pairing/docs.
files at risk — files that would lose coverage if they left (bus-factor style impact).
Compare active vs gone rows when planning coverage after departures.

Tips

Configure [teams] in .okulo.toml for a team column and better coordination context.
Do not use as a personal scoreboard — see Concepts → Responsible use.

okulo people