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 a graph.

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

The explorer lets you follow that graph. There is also a guided tour that walks through the codebase and links each explanation to the files it is talking about.

A 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 automatically trigger updates to its graph.