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.
specific aesthetic means raw claude slop w/o changing anything about it? that's no lazy extrapolation my dude. I'm just saying it lowers the value of the project, bc I can assume that it's probably not gonna be touched any further (without throwing shade on op, I think it's a cool idea. it's just way behind it's potential bc of the claude copy and the claude design in the report). it's a few commits made by claude, I assume there was no real work on the side of op. that lowers my felt value of the project. that's neither lazy nor unfair, it's the last 2 years of vibecoding? if op decides to clean it up, I'd be happy to explore it actually.
I kinda do measure projects by human effort. I don't know why you're throwing shade bc you seem to disagree.
> Ironically this tiny utilty was produced to make keeping up with Ai code a little easier.
which is fine. I just think we're losing something important when we reduce friction and effort. and for me--totally personal preference--keeping raw claude output is just that. I don't wanna throw too much shade on you or your project tho, that wasn't my intention. I'm just fed up with the moronic way of how claude writes, designs, etc.
I don't totally disagree with you and have been feeling a bit guilty of posting this work as my own when in fact it is generated by Claude, even though I try and make it clear that much of the code is generated.
I have never been able to produce this volume of work so it is very tempting to let it all hang out, so to say
The concepts are all mine and I am really happy to be able to give back to the open source community albeit a small gesture.
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.
Ironically this tiny utilty was produced to make keeping up with Ai code a little easier.
my advice to you is to write code that manages Ai, I dont think Ai is going away any time soon...
which is fine. I just think we're losing something important when we reduce friction and effort. and for me--totally personal preference--keeping raw claude output is just that. I don't wanna throw too much shade on you or your project tho, that wasn't my intention. I'm just fed up with the moronic way of how claude writes, designs, etc.
I have never been able to produce this volume of work so it is very tempting to let it all hang out, so to say
The concepts are all mine and I am really happy to be able to give back to the open source community albeit a small gesture.
I never felt any malice in your comments btw.