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.
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
It's ironic you didn't put any effort into calling out the lack of effort put in the project. Btw, the project README is fine, this is AIslop hysteria.
Idk, the project looks good to me, you are the one making claims and not backing them up properly. To me you just disagree with this specific aesthetic choice and are lazily extrapolating to the rest of the project just in case the comment could catch some upvotes.
I can see this approach being useful across non-Go repositories too.
[0] https://dev.fast/
[1] https://github.com/pingdotgg/t3code
it's a cool idea, but reads super sloppy, sorry. There is literally no effort in this.