Alternatives
Products that do what Codeknow – Architecture health scores for any codebase, no LLM needed does
Turn any codebase into a queryable knowledge graph. Simulate changes, discover features, analyze architecture. - asalsali/codeknow
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8CK
Hey HN! This is Divit from Almanac (YC S26). We built CodeAlmanac, a wiki for your coding agents that updates as you talk to them. It is open-source, local, and free. Here’s a demo: https://www.youtube.com/watch?v=XNQWV3TFBWM Your CC/Codex conversations contain a LOT of knowledge that is forgotten because it was never documented. People have their own methods of documenting their chats. We used to make Markdown files like MANUAL.md and DESIGN.md, and would prompt Claude to keep them updated. The problem is that these files quickly become outdated and messy, and there’s…
Jul 2026 · github.com
- 9AC
2018 · github.com
- 10WC
Hi all, I'm Ivan, and together with Alex, we're building a diagram visualization tool for codebases. Alex and I are devs, and we've noticed that recently we've been super productive at writing code (prompting :D). But when it comes to understanding big systems, prompting doesn't work that well — for that, diagrams are best imo. Most tools out there don't scale to big projects (e.g. PyTorch), so we're building CodeBoarding — a recursive visualizer for codebases. It starts from the highest level of abstractions and lets you dive deeper. We use static analysis and LLM agents. The control-flow…
2025 · github.com
- 11CV
I worked as a software engineer at Amazon, SAP, and on open source. In all 3 places I have struggled with the friction of understanding codebases before I can make a contribution. I think this brain-fatiguing process can be improved. I am trying to solve it with a tool I built over the last 4 years called CodeCanvas: https://docs.code-canvas.com CodeCanvas visualizes codebases through interactive diagrams linked directly to source code. Users can record 'simulations' to demonstrate data flow and business logic. I’ve also recently added an LLM chat where it takes only the relevant…
2025 · pie-crepe-38f.notion.site
- 12AP
As a former CIO who managed teams working with millions of lines of legacy code (Visual Basic, Sybase, Oracle Forms, and worse), I feel the pain of maintaining and onboarding developers to legacy systems. Believing that LLM-enabled tools can play a role in solving this, I've built a tool that automatically generates documentation for legacy codebases using the Model Context Protocol (MCP) & Claude Sonnet. At first glance, I think this approach has merit. Some samples are in the README. I welcome your thoughts. The Problem: - Legacy codebases are notoriously difficult to understand and…
2025 · github.com
- 13GB
Hey HN, We’re excited to share PySpur, an open-source tool that provides a graph-based interface for building, debugging, and evaluating LLM workflows. Why we built this: Before this, we built several LLM-powered applications that collectively served thousands of users. The biggest challenge we faced was ensuring reliability: making sure the workflows were robust enough to handle edge cases and deliver consistent results. In practice, achieving this reliability meant repeatedly: 1. Breaking down complex goals into simpler steps: Composing prompts, tool calls, parsing steps, and branching…
2024 · github.com
- 14
- 15TS
Code review is the new bottleneck. "Tests passing" is no longer sufficient to trust the changes, and the (human) cost of evaluating the quality and robustness of new agent-written contributions is skyrocketing. We built Topos to evaluate code quality based on the structural properties of the programs themselves. We map your files to graphs (AST, CFG, CPG, MDG) and calculate metrics that can characterize how simple, composable, or secure your programs are. Agents can use this tool as they write and optimize based on your preferences. And yes, the inspiration for the repository is from…
Jun 2026 · krv.ai
- 16AO
Hi, We are building an open-source framework for loading and structuring LLM context to create accurate and explainable LLM answers using knowledge graphs and vector stores. We built the tool with four main concepts in mind: 1. Loader -> uses dlt in the backend to load and structure the data 2. Cognify step -> creates a graph with summaries, labels and factoids that are interconnected across the documents and stored as a representation in the vector store 3. Optimizer -> Uses DSPy to optimize LLM queries, and we plan to extend it to most of the knobs we can turn, like chunking etc. 4. Search…
2024 · github.com
- 17NT
I built a CLI tool that turns codebases and PRs into diagrams so you can quickly understand how things fit together. Originally made it because I couldn't follow my own AI-generated repos. Just shipped a big update: - Switched from D2 to Mermaid for rendering - Tree-sitter AST parsing + agentic flow instead of raw LLM calls. ~50x faster. - Works on any GitHub repo or PR, not just local - Dropped the web frontend, it's just a CLI now - Published as a pip package Still a ton to improve and I'm building fast. Feedback, issues, PRs all welcome.
Feb 2026 · github.com
- 18IB
After years of struggling with onboarding to new projects, I got tired of spending weeks just trying to grasp the basics of a codebase. The README rarely tells the whole story, and "just read the code" isn't practical for large repos. I built RepoIQ to create personalized learning paths through any GitHub repository. It analyzes the codebase structure, identifies key components, and creates a step-by-step guide tailored to your learning needs.
2025 · repoiq.be
- 19LB
Liven Beta scaffolds your codebase’s dependency graph—functions, classes, cross‑file & folder relations—and displays it instantly in the terminal. Think of it as a context engine for developers and LLMs.
2025 · github.com
- 20IE
Hi HN! GitSummarize is an open-source devtool that I made this weekend. Given any public GitHub repository it generates high-quality documentation from the codebase using Gemini 2.5 Pro. Specifically, it tries to extract the tribal knowledge, business logic/rules embedded within codebases. Pro Tip: You can replace "hub" with "summarize" in any repository URL to access its documentation. I created this because there was a steep learning curve to understanding some of the open-source codebases out there while getting started with contributing. Having detailed documentation would be…
2025 · gitsummarize.com
- 21A1
I've seen a lot of comments about how complex frameworks like LangChain can be. Over the holidays, I wanted to see how minimal an LLM framework could get if we stripped away everything non-essential. The result is an LLM framework in just 100 lines of code. These 100 lines capture what I see as the core abstraction of most LLM frameworks: a nested directed graph that breaks down tasks into multiple LLM steps, with branching and recursion to enable agent-like decision-making. From there, you can layer on more advanced features like agents, RAG, task decomposition, and more. I’ve intentionally…
2025 · github.com
- 22LT
Measures the ability of various LLMs to navigate a fictional codebase via iterative directory tree expansion and observation. Each model's baseline ability is compared against combinations of various prompt engineering mods to quantify exactly how much they help or hinder the LLM. Interesting findings here: https://github.com/aiwebb/treenav-bench#interesting-findings
2024 · github.com
- 23OD
I’d like to use LLMs for remembering all kinds of things: fitness, to-do lists, contacts, bug reports, research links, whatever. But there is no way to do that now. For example, if I find a great coding tutorial in chat, or tell it how much I ran yesterday, it forgets that when I close the chat. Even if I keep the chat history, I still need to scour through lots of messages to find the data I want. Ideally, Claude would remember all this, and I’d be able to find it later with ease. This is what my team built. It is a collaborative database you add to any LLM that supports MCP. (Claude Code,…
2025 · dry.ai
- 24LA
Hello HN, I am building a devtool to understand existing codebases. The idea originates from my time at big tech as well as various attempts to get involved in open source projects. When I was in college I wanted to improve my coding skills by contributing to opensource projects. I would pickup a bug or feature request but I always found myself stuck at the very first step. I did not understood where and how to begin contributing. I once submitted a patch in firefox which was labeled "Good first issue" but that was still very handheld. The assigner told me exactly which files I need to…
2024 · lucidcode.ai
Ranked by how close each launch is in meaning, then by votes. Refine with a description →