The generated docs include a system overview, architecture breakdown, key modules, tech stack, entry points, and dependencies.
There’s also a Q&A chat to ask follow-up questions about the repo.
Why I built this:
I think we’re heading toward a world where most code is written by AI agents, and the bottleneck shifts from writing code to understanding what was written. Traditional docs assume a human author. I wanted something that could explain any codebase instantly, regardless of who (or what) wrote it.
Some details:
* Each repo is indexed once and cached permanently
* Login required via GitHub OAuth (one free repo per account)
* All generated docs are public by default
* It’s open source: github.com/stym06/quickgithub
Would love feedback on the quality of the generated docs.
Try it on a repo you know well and tell me where it gets things wrong. that’s the most useful feedback I can get.
1. Ask a question in natural language
2. Kepler finds relevant tables and recalls past learnings
3. The AI agent generates SQL, executes it read-only, and validates results
4. Results appear with suggested charts when appropriate
It features persistent memory - it learns corrections, schema notes, and patterns across sessions, implemented using Qdrant + Ollama (nomic-embed-text).
off topic, but prometheus pushgateway is such a bad implementation (once you push the metrics, it always stays there until it's restarted, like counter does not increase, it just pushes a new metric with the new value) that we had to write our own metrics collector endpoint.
> "But I got it all working; now I can finally stop explaining to my boss why we need to re-structure the monitoring stack every year."
Prometheus and Grafana have been progressing in their own ways and each of them is trying to have a fullstack solution and then the OTEL thingy came and ruined the party for everyone
Yes there are a lot of bugs since I just wrote this in one sitting today. Will be fixing all of this. For log rotation, I'll sort by the last_modified_at ts and then purge those
That sucks! Now I'm thinking my github action that is doing a `git pull repo && cd repo/ && rm -rf dist/ && populate.sh && git push` in my bash script will totally go rogue one day and kill everything. Any idea, peeps?
The idea is simple: take any GitHub URL, add “quick” before github.com, and get AI-generated system design documentation in under 60 seconds.
github.com/vercel/next.js → quickgithub.com/vercel/next.js
The generated docs include a system overview, architecture breakdown, key modules, tech stack, entry points, and dependencies.
There’s also a Q&A chat to ask follow-up questions about the repo.
Why I built this:
I think we’re heading toward a world where most code is written by AI agents, and the bottleneck shifts from writing code to understanding what was written. Traditional docs assume a human author. I wanted something that could explain any codebase instantly, regardless of who (or what) wrote it.
Some details: * Each repo is indexed once and cached permanently * Login required via GitHub OAuth (one free repo per account) * All generated docs are public by default * It’s open source: github.com/stym06/quickgithub
Would love feedback on the quality of the generated docs.
Try it on a repo you know well and tell me where it gets things wrong. that’s the most useful feedback I can get.