Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Transform your codebase into a single Markdown doc for feeding into AI

tesserato.web.app

Post reply on HN
Print view View original

21–30 of 172 posts

Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI

#21

Post by hk__2 »

Keyframe wrote: post #19

Wouldn't it be wonderful to have a tool where you interact with AI interactively through the codebase via IDE / vim / emacs tree? Say, you open your codebase and start with prompts and AI+tool navigates to a function or a place where it needs to and modifies stuff while chatting to you about it? Or you jump to somewhere, highlight where you are to scope down the focus of it (while it still retains all of the code in…

I tried various solutions but I still haven’t found a chat tool that allows me to navigate a large monorepo. I’d like to be able to say "open the file where there is the function to do ", but current tools don’t understand that.

Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI

#22

Post by ycombinatornews »

ainiriand wrote: post #2

My codebase sitting at 4M lines: hold my spaghetti.

You can ask Cursor to use information from specific folder (aka your 4M lines) and it would summarize it and use that.

Not a replacement for full 4M lines but it might work for some tasks/prompts

Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI

#23

Post by zknowledge »

Keyframe wrote: post #19

Wouldn't it be wonderful to have a tool where you interact with AI interactively through the codebase via IDE / vim / emacs tree? Say, you open your codebase and start with prompts and AI+tool navigates to a function or a place where it needs to and modifies stuff while chatting to you about it? Or you jump to somewhere, highlight where you are to scope down the focus of it (while it still retains all of the code in…

Apologies if I'm missing something, but aren't you describing Cursor/Copilot/Windsurf?

Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI

#25

Post by imdsm »

akoculu wrote: post #5
pmx wrote: post #4

How does this compare to / differ from https://github.com/yamadashy/repomix ?

or https://github.com/azer/llmcat

I simply have a bash script called printall which takes in some args, and outputs markdown codeblocks with filenames and a tree. One of hundreds of scripts built up over the years.

Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI

#26

Post by tempoponet »

A new tool like this comes out every week, and that's great! But I think it's fair to ask how this compares to popular ones like RepoMix? Anyone keeping an eye on this space will want to know why this is different from what's already out there and being used.

Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI

#29

Post by rapind »

Somewhat related. I built an Elm app all in one file as an experiment and to see if I like it. It's a little over 7k lines and I'm occasionally adding more to it.

It's actually pretty straightforward if you're in a language with lexical scoping, and it simplifies some things, like includes / cyclical, no modules, no hunting through files, etc.

I feel like this set up could integrate really well w/ AI models.

I've found that the only real limitation, at least in my experiment, was a lack of decent editor support. I use vim so this wasn't really much of an issue for me with many great ways to navigate a file, and a combination of vertical and horizontal splits on a large screen, but when I opened it up in other "modern" editors the ergonomics fell apart quite a bit.

I think the biggest downside was re-using variable names between large scopes occasionally made it hard to find the reference I wanted (E.g. i, x, key, val), but again, better editor support allowing you to limit your search to within the current scope would help. Also easily mitigated with more verbose throwaway variable naming.

Post reply on HN