What does git-who do that git blame cannot?

git-who ranks contributors per file or directory across thousands of files quickly, with filtering, TUI display, and caching. git blame is line-by-line and unusable at scale.

How much engagement did git-who get?

252 HN points, 127 comments, March 2025. 2,679 GitHub stars.

What is the main limitation users reported?

Multi-email deduplication: same person committing from work and home email is counted as two people. HN top comment flagged this.

Is there a commercial opportunity?

A git blame TUI with team-aware identity deduplication and ownership export (CSV/JSON) does not exist. git-who is OSS, solo developer.

The primary HN thread is from March 2025, making this signal 15 months old. Low confidence on current demand vs newer signals like RTK or Lowfat.

← Back to dashboard

clawsmith.com/signal/git-who-industrial-scale-git-blame-attribution-cli

🔥 HypeUnderserveddev_tool_cliLive

No fast CLI for industrial-scale git blame that ranks contributors per file or directory with filtering

GitHub's Contributors tab is slow and coarse. git blame line-by-line is unusable at scale. Developers need to answer ownership questions across thousands of files quickly for code reviews, security audits, and onboarding. git-who (252 HN pts, 127 comments, March 2025, 2.7k GitHub stars) surfaces this demand. Multi-email deduplication and fast caching are the unresolved gaps.

Product Idea from this Signal

A CLI tool that ranks code authorship and ownership across a whole repo and routes reviewers

3.5k ▲

Developers cannot answer who owns a file or directory quickly because git blame works line by line and CODEOWNERS is a static config that drifts from reality. This is a fast command line tool that walks the full commit history of any repo, ranks real contributors per file and per directory with team aware dedup and filtering, and turns that into reviewer routing and an exportable ownership map.

GITCLICODE_OWNERSHIPDEVELOPER_TOOLSCODE_REVIEWREPO_ANALYSIS

Competitive183 leadsView Opportunity →

Score Breakdown

GitHub

2,737

379

Social Proof 2 sources

sinclairtarget/git-who: A new CLI tool for industrial-scale Git blaming

gh:sinclairtarget · 12/7/2024

2,737 HN

Show HN: Git who – A new CLI tool for industrial-scale Git blaming

weebst · 3/18/2025

379

Gap Assessment

UnderservedExisting solutions leave gaps

git-who is the only dedicated CLI. GitHub's native view is browser-only and aggregate. Clear opportunity for a git blame TUI with team-aware dedup and ownership export

Frequently Asked Questions

Virality Score

3,116

across 0 platforms

Details

Signalhype

Ecosystemdev_tool_cli

Sources2

Platforms0

Updated1d ago

Trend→ stable

Top ideas

All ideas →

0A static linter that audits MCP server code for 2026-07-28 stateless spec compliance and flags every breaking change before it ships 0A CLI tool that automates full migration from Gemini CLI to Antigravity CLI 0A web app that attributes and hard-caps AI coding assistant spend across seats, credit pools, and agent runs for engineering orgs