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.
peter_retief 7 minutes ago [-]
Just Go for now.
.. useful across non-Go repositories too. yes
order-matters 2 minutes ago [-]
why Go
joe-esquibel 46 minutes ago [-]
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.
stigok 2 hours ago [-]
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.
48 minutes ago [-]
baalimago 1 hours ago [-]
Interesting! It would be cool to see this as a cli tool to allow agents to efficiently inspect codebases
dmoose 22 minutes ago [-]
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
slantedview 1 hours ago [-]
This is really cool. I could see adding this alongside the godocs to my open source projects.
Rendered at 17:32:58 GMT+0000 (Coordinated Universal Time) with Vercel.
I can see this approach being useful across non-Go repositories too.