reddit · SideProject · 09-18 07:50 47 分 ← 返回列表

Kin - an open source repo that records what calls what, so search stops burying the answer

Before you change a function, you want to know every place that uses it, because anything you miss can break. The usual way to find out is to search for its name. The trouble is that search matches every line containing that word. A real example from the GitHub CLI codebase. It has a function called Title . Search for Title and you get 431 lines. According to the compiler, only 6 of them actually use that function. The other 425 just happen to contain the word Title. That leaves you, or

五维评分

付费意愿

需求真实度

个人可落地

竞争空间

新鲜度

AI 分析

痛点：文本搜索会返回大量同名误匹配，开发者或 AI 编码代理很难快速定位真正调用某个函数的代码位置。

目标用户：需要重构、理解大型代码库的开发者，以及为 AI 编码代理提供代码上下文的工具团队。

证据：Search for Title and you get 431 lines. According to the compiler, only 6 of them actually use that function. The other 425 just happen to contain the word Title. That leaves you, or your AI coding agent, sorting 6 real uses out of 431 matches.

变现：开源核心 + 团队版/云索引/企业本地部署收费；IDE/CI 插件订阅；为 AI 编码代理提供付费 API 或 MCP 服务。

MVP：针对 TypeScript 或 Python 做 CLI + IDE 插件/MCP server：用 tree-sitter 或 LSP 建立函数级调用图，支持“谁调用了这个函数”查询并输出精确调用点；先不做完整 Git 替代。

竞品：Sourcegraph、GitHub Code Search、Sourcetrail、CodeQL、IDE Find Usages/LSP、Glean

摘要：作者发布开源工具 Kin，试图用随提交保存的函数调用图替代文本搜索，解决开发者与 AI 编码代理找错调用点的问题。示例中 GitHub CLI 的 Title 函数被文本搜索返回 431 行，编译器确认仅 6 处真实调用。项目痛点真实且量化，但未展示付费用户、收入或外部验证。