Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

GitHits

Code example engine for AI agents and devs (Private Beta)

Details

External ID
46105112
Source
HN
Company
—
Product
GitHits
Website domain
githits.com
Launched
Dec. 1, 2025
Cohort
—
Upvotes
11
Upvotes percentile
0.5286259541984732
Tags
—
Fetched at
Sept. 7, 2026, 9:25 p.m.
Updated at
Sept. 7, 2026, 9:25 p.m.

Description

It has been almost 10 years since I started the opencv-python packaging project. Scaling it to more than 100 million downloads as a side project showed me how much ease of installation and proper package distribution matter to users. It gave the computer vision ecosystem a noticeable boost. Now I have a new idea that I hope can help even more people across the broader software engineering world.A while ago, I realized I kept giving the same advice to teammates and friends when they ran into a programming issue they couldn't easily solve: go to GitHub and look at how others solved it.There is a huge pool of underused example material across open source. Most problems developers face are not that novel. With enough digging, someone has already solved the same issue in code or at least posted a workaround to an issue or discussion thread.The trouble is that GitHub search is limited and works only when you already know the right keywords. You also need the time and patience to go through and read all the results, connect information across files, repositories, issues, discussions, and other metadata, and then turn that into a working solution. The same limitations apply to Stack Overflow and other search tools.LLMs changed a lot, but they did not change this. They do not perform equally well across all programming languages, and their training data is always stale. They cannot reliably show how to combine multiple libraries in the way real projects do. For these and many other cases, they need a real, canonical code example rather than an outdated piece of documentation written for humans.That is why I started building GitHits. It is designed to handle the work that humans and AI coding agents struggle with: finding real solutions in real repositories and connecting the dots across the open source ecosystem.GitHits searches millions of open-source repositories at the code level, finds real code and surrounding metadata that match the intent of your blocker, and distills the patterns it finds into one example.The initial product is in private beta, with MCP support to connect GitHits to your favorite coding agent IDE or CLI.What makes it different from Context7 and other generic documentation search tools:- It is built around unblocking, not general search- It does not require manual indexing jobs- It works for humans through the web UI and for agents through the MCP- It clusters similar samples across repositories so you can see the common path real engineers took- It ranks the sources using multiple signals for higher quality: the selected sources might be, for example, a combination of code files, issues, and docs- It generates one token-efficient code example based on real sourcesIt is not perfect yet. Right now, GitHits supports only Python, JS, TS, C, C++, and Rust. More languages and deeper coverage are coming, and I would appreciate early feedback while the beta is still taking shape. If you have ever lost hours stuck on a blocker you knew someone else had solved already, I would love to hear what you think.

Enrichment

Theme
git and repository workflow tools
Vertical
Horizontal
Function
Search & retrieval
Audience
Developer
AI stance
AI feature
Project type
Commercial product
Normalized one-liner
code example search for ai agents
Manually corrected
False

Could you build this?

Partial Building the search API and interface is straightforward, but indexing, parsing, and maintaining a version-aware AST search index across massive open-source repositories requires substantial infrastructure and data engineering.

What it would actually take: The system requires an ingest pipeline cloning open-source package repositories, Tree-sitter or LSP parsers to extract semantic symbol graphs and code examples across language versions, and a hybrid vector/sparse search backend (like Tantivy or Milvus). The hard part is deduplication, parsing millions of code snippets incrementally, and managing storage and index latency at scale. It requires experienced search infrastructure and data pipeline engineers.

Discussion

4 comments analyzed.

Concerns raised: Cross-language pattern search is unreliable and not yet feasible, Results quality degrades for unofficially supported languages, Language-specific organization limits learning transfer across tech stacks

Feature requests: Generic search mode not tied to single language, Better support for architecture and UX pattern discovery across languages, Official support for more programming languages

Competitors

Other products that read as similar to this one — 244 launches clear the similarity bar, closest 8 shown.

Attention rank: #127 of 245 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 30 days after the earliest competitor.

Other launches for this product