Alternatives
Products that do what DevMem does
Ur codebase has a memory now.updates itself on every commit.
- 1
- 2IM
2018 · github.com
- 3
- 4
- 5IR
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
- 6WS
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
- 7
- 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
- 9
- 10GC
2023 · github.com
- 11DG
Devlog is a powerful tool that automatically generates (b)log posts from your Git commit history, providing a natural language summary of your development progress. It uses ollama to generate the blog posts locally so it never sends your data to third-party servers.
2024 · github.com
- 12
- 13
- 14
- 15
- 16
- 17GA
GAC is a tool I built to help users spend less time summing up what was done and more time building. It uses LLMs to generate contextual git commit messages from your code changes. And it can be a drop-in replacement for `git commit -m "..."`. Example: feat(auth): add OAuth2 integration with GitHub and Google - Implement OAuth2 authentication flow - Add provider configuration for GitHub and Google - Create callback handler for token exchange - Update login UI with social auth buttons Don't like it? Reroll with 'r', or type `r "focus on xyz"` and it rerolls the commit with your feedback. You…
Oct 2025 · github.com
- 18IR
I don't know Rust. Friday after work I realised that 90% of my IDE time now is just the commit/diff view — and even good IDEs feel heavy for that. So over the weekend I built a dedicated native tool for just that. Kyde is a macOS git commit + diff editor with one goal: be fast, do Git well. I'm curious whether anyone else mostly opens their IDE for git operations these days. It's open source, and there's a signed app in Releases.
Jun 2026 · github.com
- 19TT
I've found it helps PR reviewers when they can look through a set of commits with clear messages and logically organized changes. Typically reviewers prefer a larger quantity of smaller changes versus a smaller quantity of larger changes. Sometimes it gets really messy to break up a change into sufficiently small PRs, so thoughtful commits are a great way of further subdividing changes in PRs. It can be pretty time consuming to do this though, so this tool automates the process with the help of AI. The tool sends the diff of your git branch against a base branch to an LLM provider. The LLM…
2025 · github.com
- 20GD
Hello HN, I’m Andrew from docs.dev (https://docs.dev/), an AI powered docs assistant. With docs.dev you can generate your docs directly from your codebase, existing docs and other context sources. We don’t believe AI will replace technical writers—our goal is to make it easier for teams to get a solid first draft that they can review, edit, and improve. Think of it as a head start, not a finished product. More info on what we’ve built below but we wanted to release a quick, 1 minute, generate docs from your codebase tool. Try it out here:…
2025 · app.docs.dev
- 21
- 22DP
devnexus is an open-source cli that gives agents persistent shared memory across repos, sessions, and engineers. It maps out dependencies and relations at the function level, builds a code graph, and writes it into a shared Obsidian vault that every agent reads before writing code. Past decisions are also linked directly to the code they touched, so no one goes down the same dead end twice. Still building it out but I would love to hear any thoughts/feedback
Apr 2026 · github.com
- 23GT
Hi guys! While working in teams, internal documentation is important. But the problem is, writing it takes much time. It doesn't end there, keeping them up-to-date is a big deal as well. I built this simple tool that analyzes your codebase and automatically generates documentation right into your Github repo. Whenever you make a new commit, it analyzes the updates and modifies the existing docs to keep them up-to-date. That means, you don't need to spend time struggling with docs again. And, the new hire won't stare at the senior for that huge undocumented codebase. It works for any team…
2024 · supacodes.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →