Skip to content
Local-First Code Insights

Code InsightsFrom Git History

Point spanical at any git repository and it tells the story of a stretch of engineering: how much was built, when, by whom, and where the codebase is getting risky. Nothing leaves your machine.

Terminal
$ cd repo-alpha
$ spanical report
last 12m (2025-08 → 2026-08) · monthly · 1 repo · UTC
Net growth +104 LOC Total now 93 LOC
Top hotspots (refactor shortlist)
src/core/engine.ts churn 3 · cx 0 · owners 3
$ spanical hotspots
$

What it measures

Every run computes from real git data

Throughput churn

Added plus deleted lines and commit counts per period, with a per-developer breakdown when you want the people view.

Hotspot ranking

Files that change often and carry complexity at once float up as a refactor shortlist. Bulk reformats sink.

Ownership and bus factor

git blame at HEAD shows who wrote the lines that survived, and which directories ride on one person.

Auto-narrated timeline

A month-by-month story of your window: dominant commits, churn spikes, and removal periods, detected for you.

Size and complexity trends

Monthly snapshots from scc at each month-end commit, so history reads as it was, not as a later cleanup made it look.

Optional ticket layer

Pull request flow, cycle time, thrash, review load and review coverage from GitHub, synced into the same local cache.

Get started in seconds

Install the released binary, or run from source

Install
$ curl -fsSL https://raw.githubusercontent.com/bhagyamudgal/spanical/main/install.sh | bash

Recommended: Quick install verifies the checksum and puts the binary on your PATH

> darwin x64> darwin arm64> linux x64> linux arm64

How it works

Four commands from first report to full ticket layer

[1]Run a report

One command inside any git repo

$spanical report
1
[2]Find the risk

The refactor shortlist

$spanical hotspots
2
[3]See who knows what

Blame-based ownership map

$spanical ownership
3
[4]Add the ticket layer

GitHub flow and review coverage

$spanical tickets
4