I used to be a heavy user of yek[0] until recently, because my workflow is basically copy and pasting back and forth to and from Google Gemini.

[0]: https://github.com/bodo-run/yek

However, as I incorporated a practice of maintaining an llms/ directory in my project (where I put various docs, e.g. .md files from llms.txt), I found that the format yek used (basically ">>>> {file name}\n{file content}") was confusing the LLM; it didn't know which files were part of your project and which files were just docs (it was editing code examples).

So I wrote my own thing which categories your files into source code files, documentation files, and other files. Each category is labelled appropriately and the LLM is able to understand what it shouldn't attempt to edit.

Here is what the output format looks like:

<category>

  <description>

    Immutable documentation FOR REFERENCE ONLY.

  </description>

  <files>

    <file>

      <path>

        llms/openai.md

      </path>

      <content>

        ...

      </content>

    </file>

  </files>

You can also pass a "task" as command line argument, and the tool will append <task>{your task}</task> to the end of the output.