Alternatives
Products that do what GitWhy does
Bring AI reasoning to every commit and PR for your team
- 1IB
https://the-pocket.github.io/Tutorial-Codebase-Knowledge/
2025 · github.com
- 2
- 3
- 4IR
Hey HN! I built a proof-of-concept for AI memory using Git instead of vector databases. The insight: Git already solved versioned document management. Why are we building complex vector stores when we could just use markdown files with Git's built-in diff/blame/history? How it works: Memories stored as markdown files in a Git repo Each conversation = one commit git diff shows how understanding evolves over time BM25 for search (no embeddings needed) LLMs generate search queries from conversation context Example: Ask "how has my project evolved?" and it uses git diff to show actual…
2025 · github.com
- 5
- 6
- 7GF
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
May 2026 · github.com
- 8GW
I've always wanted a better way to explore the authorship data embedded in a Git commit log. I'm having fun building a CLI tool to do this. It's a bit like the "Contributors" tab on Github that shows you how many commits each contributor has made but much faster and with many more options. If you get a chance to try it out, please let me know. I'd love to hear feedback and suggestions. Thank you!
2025 · github.com
- 9WG
2022 · github.com
- 10
- 11WS
I’ve been in the MLOps space for ~10 years, and data is still the hardest unsolved open problem. Code is versioned using Git, data is stored somewhere else, and context often lives in a 3rd location like Slack or GDocs. This is why we built XetHub, a platform that enables teams to treat data like code, using Git. Unlike Git LFS, we don’t just store the files. We use content-defined chunking and Merkle Trees to dedupe against everything in history. This allows small changes in large files to be stored compactly. Read more here:…
2022 · xethub.com
- 12
- 13
- 14IV
GitDiagram is an open-source micro dev-tool that I made this past week Given any public GitHub repository it generates diagrams in Mermaid.js with Claude 3.5 Sonnet I extract information from the file tree and README for details and interactivity (you can click components to be taken to relevant files and directories) Also, you can replace "hub" with "diagram" in any repository URL to access its diagram I created this because I wanted to contribute to open-source projects but quickly realized their codebases are too massive for me to dig through manually, so this helps me get started I do…
2024 · gitdiagram.com
- 15
- 16
- 17GA
Simon(sfarshid) and I spend a lot of time on GitHub. As data nerds we put together a quick tool to explore your repository’s data. How it works: - Data Loading: We use dlt to pull data (issues, PRs, commits, stars) from GitHub - Semantic Layer: Relta wraps the underlying dataset into a semantic layer so the LLM doesn’t hallucinate. - Text-to-SQL: A text-to-SQL agent transforms your plain-English question into a query using the semantic layer - Generative Charts: assistant-ui dynamically generates a chart based on the SQL query - Refinements: If the semantic layer can’t handle your question,…
2024 · github.com
- 18
- 19WG
Hey there HN! We're Esteban and Esteban and we are looking to get feedback for the new version of our GPT-powered, open-source code contextualizer. We're starting with a VS Code extension that indexes information from git (GitHub, GitLab, or Bitbucket integrations available), Slack and Jira to explain the context around a file or block of code. Finally, we summarize such aggregated context using the power of GPT. As devs we know that it's very annoying to look at a new codebase and start understanding all the nuances, particularly when the person who wrote the code already left the company.…
2023 · watermelontools.com
- 20
- 21GB
Feb 2026 · blog.rbby.dev
- 22GN
Hey folks, Here's a quick and dirty tool to use natural language to get git to do what you want. Example: $gitgpt create a new branch called feature/test add all the files and commit with msg creating feature test then push to origin I haven't put it through the wringer yet, however it's worked well with some pretty straight forward day to day git usage.
2023 · github.com
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →