Seems great: I looked at two largish code bases I'm familiar with, and learned something each time.
But is this just a summary for the impatient, or can it reduce the effort for developers writing docs?
Docs have always been the mirror of code, and thus hard to get and keep right. Can we do without the mirror, or parts of it?
Does it work when you haven't written documentation for your code? Let's say one is fanatical about writing such clear code that names are sufficient to convey what's happening (i.e., no documentation and no comments). Does it work?
If not, does it work when there are only (clear) comments?
Does it tell you when documentation, comments, or code is unclear or missing?
I.e., I'd like it to go beyond summarization to fill easy gaps and point developers to the hard ones.
The marketing blurbs on point are not helpful.