Alternatives
Products that do what Digest Diff does
Let your commit history tell its story using the power of AI
- 1
- 2
- 3
- 4
- 5
- 6
- 7GH
2021 · simonwillison.net
- 8
- 9
- 10WO
Hi HN, I've been using Claude Code etc. for nearly all my work lately, and I wanted to see how many of my commits it was actually co-authoring. So I made this little tool to visualize my usage. You log in with Github (read-only), it scans your commits from the last year, and visualizes how many came from Claude, Cursor, or any tool that adds Co-Authored-By trailer to the commit message. Caveat: not all tools add this trailer, so this doesn't include e.g. Codex. Still, hope you find it interesting!
Mar 2026 · technically-your-name-is-on-it.btao.org
- 11GS
Hunk-by-hunk and line-by-line staging for git, designed for building clean commit history! Writing code is messy. Git history doesn't have to be. During development we experiment, refactor, backtrack, and fix mistakes. If every step ends up as a commit, the history becomes noise. A curated history turns that process into a clear sequence of logical changes. git-stage-batch helps you build that history incrementally by letting you stage changes hunk-by-hunk or line-by-line, shaping commits around meaning instead of the order the edits happened.
Apr 2026 · github.com
- 12LA
I built this tool that auto-commits your code when you run an experiment, storing structured metadata in the commit message. A bit like `wandb` but local. There is a small CLI that lets you query for (e.g.) `metrics.accuracy > 0.9`, to find the code state that produced a good results. This is the first release, and there are quite a few planned features if anyone wants to submit a PR.
2025 · github.com
- 13IC
Hey HN, I built ShadowGit a while back to automatically commit code every minute to a hidden git repo (.shadowgit.git). Original goal was to easily rollback when AI tools break things. But I discovered something interesting: this minute-by-minute history is perfect context for AI assistants. So I built an MCP server that lets Claude/Cursor query this history using native git commands. The results surprised me: Before: Claude would read my entire codebase repeatedly, burning 15,000+ tokens to debug issues. After: Claude runs `git log --grep="drag"` finds when drag-and-drop worked,…
2025 · shadowgit.com
- 14CT
2016 · commit.ws
- 15VG
Visualize and analyze complete Git commit histories as animated force-directed graphs. See how commit density, branch activity, and contributor participation evolve over time. Live site: https://nshcr.github.io/git-commits-threadline/ This project helps you quickly inspect: - repository growth over long time ranges - branch structure and active thread distribution - contribution patterns across maintainers and collaborators
Mar 2026 · github.com
- 16DA
2016 · digest.ai
- 17GT
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
- 18TA
Git AI is a side project I created to track AI-generated code in our repos from development, through PRs, and into production. It does not just count lines, it keeps track of them as your code evolves, gets refactored and the git history gets rewritten. Think 'git blame' but for AI code. There's a lot about how it works in the post, but wanted to share how it's been impacting me + my team: - I find I review AI code very differently than human code. Being able to see the prompts my colleagues used, what the AI wrote, and where they stepped in to override has been extraordinarily helpful. This…
Nov 2025 · usegitai.com
- 19AP
As a former CIO who managed teams working with millions of lines of legacy code (Visual Basic, Sybase, Oracle Forms, and worse), I feel the pain of maintaining and onboarding developers to legacy systems. Believing that LLM-enabled tools can play a role in solving this, I've built a tool that automatically generates documentation for legacy codebases using the Model Context Protocol (MCP) & Claude Sonnet. At first glance, I think this approach has merit. Some samples are in the README. I welcome your thoughts. The Problem: - Legacy codebases are notoriously difficult to understand and…
2025 · github.com
- 20AS
Hi HN, I built a simple tool that summarizes your team’s git logs into a weekly update that teams can send to leaders, other teams, etc. I hated writing the same update multiple times a week to everyone asking “what’s the status of X” Copy your repo’s commit logs with git log —all —since=“1 week ago”, paste them, and get a well-formatted update. Planning to add Github integration to further automate. Curious what folks think.
2024 · syncup.ai
- 21AL
Feb 2026 · claude-commits.vercel.app
- 22WA
Today you can easily adopt AI coding tools because you have git for branching and rolling back if AI writes bad code. We haven't seen this same capability for data and decided to build it ourselves. Nile is a new kind of data lake, purpose built for using with AI. It can act as your data engineer or data analyst creating new tables and rolling back bad changes in seconds. We support real versions for data, schema, and ETL. We'd love your feedback on any part of what we are building - https://getnile.ai/ What do you think?
Jan 2026
- 23AD
2025 · github.com
- 24
Instant CLI & Web to turn git diff into Conventional Commits
5d ago · ai-commit-tool.ikeda-lef.workers.dev
Ranked by how close each launch is in meaning, then by votes. Refine with a description →