HN Explorer

15 comments

[ 2.5 ms ] story [ 9.7 ms ] thread
stigok
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.
baalimago
Interesting! It would be cool to see this as a cli tool to allow agents to efficiently inspect codebases
dmoose
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
lukasschwab
Agents are pretty savvy with the `go doc` and `go list` builtins, especially if you nudge them!
slantedview
This is really cool. I could see adding this alongside the godocs to my open source projects.
quibono
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
Just Go for now. .. useful across non-Go repositories too. yes
[deleted]
(comment deleted)
joe-esquibel
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.
tortela
would be nice if there was a picture of the final result in the README.md
RamblingCTO
> 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.

gchamonlive
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.
RamblingCTO
And what would effort look like, besides inspecting code and the result to find the message I quoted, huh?