Looking for feedback on my in-progress tool: RepoGraph…
0 reactions
Looking for feedback on my in-progress tool: RepoGraph — repository intelligence / codebase analysis
Hey,
I’ve been working on a tool called **Repograph** and wanted to get some feedback from people who work with real codebases.
The basic idea is to help understand repos better by building a graph of the codebase and surfacing useful stuff from that. Things like call relationships, execution pathways, entry points, dead code signals, variable flow, architecture-level inspection, impact analysis, etc.
It currently has a CLI, Python API, and MCP server, and right now it supports Python, JavaScript, and TypeScript.
It’s still very much a work in progress, so I’m not posting this like it’s finished or production ready. I mostly just want honest opinions on whether this actually looks useful, what seems unnecessary/overcomplicated, and what feels missing.
Repo:
https://github.com/SillySerpent/Repograph
A few things I’d especially like feedback on: does this solve a problem people actually care about, does the output seem useful for understanding/debugging repo, what feels confusing, overengineered, or not worth keeping, what features would make it more useful in practice, whether the docs/setup make sense from a new user perspective and what kind of workflows or repo sizes this seems most suited for
Blunt feedback is completely fine. If parts of it seem impractical or just not that useful, I’d rather know now than later.
Thanks.
#technology
source
Hey,
I’ve been working on a tool called **Repograph** and wanted to get some feedback from people who work with real codebases.
The basic idea is to help understand repos better by building a graph of the codebase and surfacing useful stuff from that. Things like call relationships, execution pathways, entry points, dead code signals, variable flow, architecture-level inspection, impact analysis, etc.
It currently has a CLI, Python API, and MCP server, and right now it supports Python, JavaScript, and TypeScript.
It’s still very much a work in progress, so I’m not posting this like it’s finished or production ready. I mostly just want honest opinions on whether this actually looks useful, what seems unnecessary/overcomplicated, and what feels missing.
Repo:
https://github.com/SillySerpent/Repograph
A few things I’d especially like feedback on: does this solve a problem people actually care about, does the output seem useful for understanding/debugging repo, what feels confusing, overengineered, or not worth keeping, what features would make it more useful in practice, whether the docs/setup make sense from a new user perspective and what kind of workflows or repo sizes this seems most suited for
Blunt feedback is completely fine. If parts of it seem impractical or just not that useful, I’d rather know now than later.
Thanks.
#technology
source
| 3,000 mlx | |
| 3 | |
| 0 |