GitChat
Giving a voice to codebases can't be a bad idea, can it?
Created on 21st January 2024
•
GitChat
Giving a voice to codebases can't be a bad idea, can it?
The problem GitChat solves
GitChat is a game-changer for developers dealing with extensive Git repositories, transforming the tedious task of navigating through massive codebases into a smooth, conversational experience. Imagine having a dialog with your codebase, where complex structures and intricate lines of code become clear, understandable conversations. This isn't just about skimming through files; it's about a deep, intuitive interaction with your repository. GitChat, powered by OpenAI's generative AI, doesn't just understand the code – it comprehends its nuances, making even the most intricate details accessible and straightforward. It's the perfect companion for those moments when you're on the brink of a breakthrough but are held back by those few perplexing lines of code. With GitChat, the entire repository is at your fingertips, ready to be explored and understood like never before.
And in more simpler words, you talk to git repos, you get smarter :D
Challenges we ran into
The primary issue that plagued this idea was to find a way to choose the correct files to prompt LLM's, paying respect to the context size that would otherwise destroy any naive approach of passing the entire codebase for a prompt, once we had that figured out by just recursively calling Openhermes-API, the problems were more of the general sort, ranging from thinking about adding session management for the first time in our developer journey without adding a login screen, or finding a way to speed up the git files metadata extraction process(which improved by over 20x compared to the initial naive method we employed in the initial stages).
Concurrency was also an issue, and while its not built up yet for a complete production level of perfection, it still manages to hold up against everything we could throw at it (which was about ten of our friends all spamming questions from their laptops ).
While there are still a lot of issues we might fix, we are confident this might just be good enough
Tracks Applied (1)
Open Track
Technologies used
