hhistuialpha
Git history, made useful

See the files your next change might miss.

histui turns repeated Git co-changes into focused evidence for refactors, bug hunts, architecture work, and coding agents—without sending your history anywhere.

Get started View source
$ go install github.com/Rounak-stha/histui/cmd/histui@latest
history / coupling
target internal/git/cli_repo.go
historically relatedscore · co-changes
01
internal/git/models.go
.857 · 18
02
internal/git/repository.go
.720 · 12
03
internal/index/store.go
.514 · 9
fresh index · 1,000 commits · 4 bulk commits excluded
< 1scached targeted query
100%local processing
SQLiteportable history index
JSON v1stable agent contract
The missing signal

Static analysis shows today.
History shows what moves together.

Repeated co-change is not proof of dependency. It is a practical clue that helps you find tests, schemas, migrations, configuration, and boundaries before editing.

01

Targeted coupling

Ask one small question: which files repeatedly changed with this file? Results are bounded, ranked, and deterministic.

histui query coupling . --file src/auth.go
02

Index once, query fast

Stream history into a local SQLite index, then incrementally refresh only fast-forward commits.

03

Built for agents

A typed Pi tool and Agent Skill provide compact context without flooding the model window.

04

Private by default

No service, telemetry pipeline, or history upload. Your repository evidence remains local.

05

Honest evidence

Freshness, history windows, ignored files, merge policy, and excluded bulk commits are explicit in every machine-readable result.

freshness: cachedbulk threshold: 200minimum evidence: 3
Three commands

From repository to useful context.

Index deliberately. Query narrowly. Validate every historical clue against current code and tests.

01

Build a bounded index

$ histui index . --max-commits 5000
02

Ask about one file

$ histui query coupling . --file src/app.go --format json
03

Refresh after new commits

$ histui index . --update
Pi integration

Historical context, on demand.

Install the extension and skill together. Pi can query cached evidence before a substantial refactor, while avoiding hidden full-history work.

Read the integration guide
git_history
{
  "file": "internal/git/cli_repo.go",
  "maxCommits": 1000,
  "freshness": "cached",
  "ignore": ["vendor", "*.md"]
}
Know before you change

Your Git history already documented the architecture.

histui makes that evidence searchable, bounded, and useful.

Read the docs Star on GitHub