Idea: Deepwiki that bridges Multiple Github Repositories?

[sng-asyncfunc]

A problem I’ve been personally intrigued by:

How can we generate a deepwiki that bridges multiple GitHub repositories......one that actually explains how they interact and fit together as a system?

One idea: treat each repo as a module, then create a top-level “orchestration layer” that traces data flow, shared interfaces, and call relationships across repos.

But I know this barely scratches the surface.

Anyone thinking about this too? How would you approach it?

[sng-asyncfunc]

Working on multi-repo support — generate a unified wiki that understands how your GitHub projects interact across repos.

Think: system-level docs, automatically mapped.

Here’s a first look at the WIP 👇
https://github.com/user-attachments/assets/fe56f072-1121-4aa5-b616-04f72dfa90fb

[joyo11]

Oh man, this is such a good question I haven’t gone super deep on it yet, but I’ve definitely felt the pain. You look at five different repos that all supposedly make up “one system,” and it’s like trying to solve a mystery without a map or flashlight.

If I were approaching this, I’d treat each repo like its own “module” pull out the APIs, shared data models, queues, etc. Then I’d try to build a map of how they talk to each other. Probably a combo of static analysis (like tracing imports, API calls) plus embeddings to find similar logic across repos and then feed that into an LLM to write actual human-readable docs like:
“Repo A sends data to Repo B via this endpoint, which then triggers a job in Repo C that yells at the database.”

Would definitely throw in some visualization too maybe even one of those interactive diagrams where you click on a service and see its whole spiderweb of connections. Basically, a smarter system README that actually knows what’s going on across codebases. Because right now, the real documentation is just Slack messages and vibes 😅

[szl97]

I ever thought about this, it may be a knowledge graph between all the repository. And it is possible to extract the subject verb object triplet relationship between systems from the graph.

Each system clarifies which one it called and shows it. The user's question should be analyzed first to determine which system it belongs to.

[zcuder]

This is a great feature to have, sometimes people have client-server sitting in different repos, if Deepwiki could bridge then would be great

[buptsaisai]

蹲，如果需要动手记得踹我

[xichengpro]

+1

[vdm]

... or a comparison of multiple repos that are not modules designed to work together or even written in the same language, but appear to at least partially overlap in the problem they are trying to solve.

For example:
https://github.com/peak/s5cmd and https://github.com/rclone/rclone
https://github.com/AIDotNet/OpenDeepWiki and https://github.com/AsyncFuncAI/deepwiki-open

[BoBoooooo]

+1

[Kukks]

+1 Maybe a quick & dirty solution would be to create a repo with all relevant git repos as a submodule?