Show HN: Codemap – one-page interactive map of any Go repository
43 points by peter_retief a day ago | 21 comments
  • stigok a day 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.
  • baalimago a day ago |
    Interesting! It would be cool to see this as a cli tool to allow agents to efficiently inspect codebases
    • dmoose 21 hours 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
    • lukasschwab 17 hours ago |
      Agents are pretty savvy with the `go doc` and `go list` builtins, especially if you nudge them!
  • slantedview a day ago |
    This is really cool. I could see adding this alongside the godocs to my open source projects.
  • quibono 21 hours ago |
    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 21 hours ago |
      Just Go for now. .. useful across non-Go repositories too. yes
      • order-matters 20 hours ago |
        why Go
        • peter_retief 20 hours ago |
          What I am using
      • quibono 20 hours ago |
        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

  • joe-esquibel 21 hours 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.
  • tortela 20 hours ago |
    would be nice if there was a picture of the final result in the README.md
  • RamblingCTO 20 hours ago |
    > 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.

    • peter_retief 20 hours ago |
      It is just the idea, for me to navigate my project code, free to use and change
    • gchamonlive 20 hours ago |
      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 19 hours ago |
        And what would effort look like, besides inspecting code and the result to find the message I quoted, huh?
        • gchamonlive 19 hours ago |
          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.
          • RamblingCTO 4 hours ago |
            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.
            • peter_retief 3 hours ago |
              In my 20+ years of coding I have produced way worse slop that Claude wrote here.

              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...

  • int0x21 16 hours ago |
    I got inspired and "vibe coded" a Perl version :) https://github.com/interrupt21h/perl-codemap
    • peter_retief 2 hours ago |
      I will add a link..