Inspiration

The inspiration for GitProse came from my frustrations navigating the history of complex software projects. Often, simply looking at commit logs and diffs doesn't readily convey the why behind changes.

What it does

GitProse allows users to explore GitLab and GitHub repositories with natural language by asking questions about commits, issues, and PRs!

How we built it

The architecture I'm considering involves a frontend for user interaction (NextJS), a backend to handle API calls, RAG processing (Google GenKit and Google ADK ), and LLM interactions (Google Gemini API).

Challenges we ran into

I ran into multi-faceted challenges. Firstly, effectively and efficiently retrieving the right context from the version history to feed the LLM for accurate and relevant answers. Secondly, building a user interface that is both intuitive and powerful enough to leverage these new capabilities will be an ongoing process.

Accomplishments that we're proud of

I am proud that this Minimum version works for questions about commits, issues, and PRs. I am planning to add more advanced semantic features about code changes and evolutions that would help developers get more insights

What we learned

Through building GitProse, even in its conceptual stages, I've learned a great deal about the potential of Large Language Models to bridge the gap between human understanding and the often technical details of version control. I've also gained a deeper appreciation for the complexities of building developer tools that need to be both powerful and user-friendly.

What's next for GitProse

I envisioned a tool that could understand the semantic meaning of code evolution, allowing developers to explore their project's history and structure more intuitively, almost through a conversation.

Built With

Share this project:

Updates