> Every Go package in github.com/peterretief/yggstore, what it builds on, and the functions in each of its files. Tests are left out.

it's a cool idea, but reads super sloppy, sorry. There is literally no effort in this.

Possibly silly question, but is this aimed at Go repos only because of some structural reason, or because this was the author's intention?

I can see this approach being useful across non-Go repositories too.

Just Go for now. .. useful across non-Go repositories too. yes

Also, just for posterity, in terms of similar solutions that I know of there's Whiteboard [0] and T3's Guide view [1]

[0] https://dev.fast/

[1] https://github.com/pingdotgg/t3code

why Go

What I am using

would be nice if there was a picture of the final result in the README.md

I like this! It would be great if it was a hosted solution where I could just add any repository to the URL, like https://pkg.go.dev/ does for the godocs.

Whats the validation strategy that you used for this? I run a similar project and I found that golden repos were needed to prevent drift. Have you stress tested this to find any limits? I compared my go work to ctags and treesitter for proof of functions found and list precision and recall.

Interesting! It would be cool to see this as a cli tool to allow agents to efficiently inspect codebases

I took a bit different approach assuming that agents can use the language servers to get structure and just trying to keep them honest. With this in a hook a lot of stuff is caught quickly without wasting a lot of context. https://github.com/dmoose/gochecks

This is really cool. I could see adding this alongside the godocs to my open source projects.