Connect Clawsmith to your coding agent. Ship products like crazy.Unlimited usage during betaGet API Key โ†’
โ† Back to dashboard
clawsmith.com/signal/git-log-natural-language-query-history-no-cli
โš  IssueUnderservedToolLive

Git log is a wall of SHA hashes and no CLI lets you query history in plain English

Developers investigating regressions, understanding why code was written, or finding when a bug was introduced spend hours with git log, git blame, and git bisect. A Show HN in January 2026 launched a tool letting users chat with git history because filtering PRs and scanning commit logs was too painful. The Ask HN 2026 wish thread explicitly requested tools for navigating complex code history with click-through function call navigation.

Product Idea from this Signal

A CLI tool that lets developers query git history in plain English and shows which functions changed instead of raw line diffs

3.1k โ–ฒ

Developers reading git history hit a wall of SHA hashes and line diffs that show which lines moved but not which functions actually broke, and AI agents fed those line diffs are measurably less accurate. This is a command line tool that answers plain English questions about a repo's history (who last touched this function, what changed in auth last month, which commits modified this class) and renders entity-level diffs at the function and class level so both humans and coding agents see what really changed.

GITCLIDEVELOPER-TOOLSCODE-SEARCHSEMANTIC-DIFFAI-AGENTSTREE-SITTER
Competitive46 leadsView Opportunity โ†’

Score Breakdown

HN
156

Gap Assessment

UnderservedExisting solutions leave gaps

gitk, tig, and lazygit exist as TUIs but none support natural language queries. Chat-with-git-history apps are very early, 2026 vintage. Wide open for a CLI-first tool.

Frequently Asked Questions