Operating-theatre
Read any public repo as if you were the new CTO.
Paste a GitHub URL. The page extracts a small set of signals from the commit log, writes a paragraph about the last 90 days, and lists three questions a fractional CTO would actually ask the team this week.
Try one of these
How this works
The page calls a small Lambda that pulls the commit log via GitHub's public API. Signals are derived in code: which file is the hot zone, which kind of commit dominates, which contributors moved, when work landed, and whether there is a coordination smell hiding in a config or registry file. No LLM. No model. The judgement is encoded in the rules and is the same every time you run it.
What it measures:
- The biggest commit, its size and what it was
- The hot zone (most-touched non-obvious file) and how it shifted week to week
- Whether the work was fix-led, feature-led, or chore-heavy
- Whether the cadence sits inside or outside business hours
- Author distribution (one-author burst, dominant author, or spread)
- Whether a config or registry file is being touched by many hands at once
It does not clone the repo, does not run code, does not read your credentials. Public commits API only. Rate-limited per IP. Results cached for six hours.