LLM: Documentation driven exploration for big codebase

(github.com)

3 points | by anhydrite 7 hours ago ago

1 comments

  • anhydrite 7 hours ago ago

    I was always quite frustrated when agents simply did not understand my questions because my words were either not in their dictionary or their meaning was at least not quite right. In my case, I had procedures that had been replaced by simple terms, and it was time-consuming to explain, during each session, every process and how my architecture worked and how its components interacted with one another.

    Also, the agent would always find many files, most of which were useless until it finally located the correct one. This was a total waste of time and, even worse, could confuse the agent and make it go nuts.

    So I created a set of skills and a script to generate structured documentation with four levels of detail, along with a set of core files containing the architectures, development processes, glossary, and a dependency matrix.

    This way, the agent can quickly start with all the basic knowledge a new developer would have on their first day.

    It is still in development, but I use it daily, so it may be updated frequently or whenever I notice something is wrong :)