Ario Barin Ostovary

Software Engineering, University of Waterloo

DocBot

I wanted the map before I started clicking through files.

Opening an unfamiliar codebase usually means clicking through files until the architecture slowly exists in your head. I wanted DocBot to do that first pass for me.

It scans the repository, groups the code into logical scopes, uses Tree-sitter to pull out symbols and dependencies, then sends parallel explorer agents into those scopes. Their findings get combined into one graph instead of becoming a pile of unrelated summaries.

DocBot's repository architecture diagram showing the map-reduce pipeline from scanning and planning through parallel exploration and rendered documentation

The React Flow explorer lets you follow that graph rather than read the whole architecture from top to bottom. There is also a guided tour that walks through the codebase and links each explanation to the files it is talking about.

A guided tour through the data models, authentication, and API endpoints. Excerpt from the team's demo.

A graph can go stale just like a README. DocBot has status and diff commands to show what has changed in the code, and git hooks to trigger updates.

It is still pre-release, with installation from source. The pipeline and explorer work, but there is more to do on packaging.