Alternatives
Products that do what Chronocodex does
Search Git history semantically. Know what changed, and why.
- 1QB
2019 · githistory.xyz
- 2GW
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
- 3GA
Gitlogue is a CLI that turns your Git commits into a typing-style replay. It visualizes diffs line by line, shows the file tree, and plays back each edit as if it were typed in real time. Key points • Realistic typing animation • Syntax-highlighted diffs • File-tree view • Replay any commit • Self-contained CLI Demo video is in the README. Repo: https://github.com/unhappychoice/gitlogue
Nov 2025 · github.com
- 4
- 5
- 6
- 7
- 8
- 9AI
2021 · git-history.jpalmer.dev
- 10GH
2021 · simonwillison.net
- 11GT
2017 · gitorials.com
- 12
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
- 13GA
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
- 14DD
Hello friends, Today I'm sharing a little tool to help you explore GitHub repositories: • https://diggit.dev This project was admittedly a big dumb excuse to play with Elm and Claude Code. I published my design notes and all the chat transcripts here: • https://taylor.town/diggit-000 Please add bug reports and feature requests to the repo: • https://github.com/surprisetalk/diggit Enjoy!
2025 · diggit.dev
- 15SY
2023 · gist.github.com
- 16RA
I built a CLI tool that lists out all the local git repos within a directory in an easy to read table format including relevant information such as last modified date and the status of branches in the repo, along with whether it is synced with remote or not. It also includes a bunch of flags to get exactly what you want in the format you want. I got this idea as I was trying organize the large amount of local git repos I had. I also found it particularly useful when traveling since I use a different device. In these cases, it is really helpful to know which local git repos I forgot to push…
2024 · github.com
- 17CS
I built a tool that stores your full Claude Code history to let you easily find and resume sessions. It has TUI, CLI and MCP interfaces. It's a single Go binary, and the session history is synced to SQLite each time you use it. Default mode is the TUI with a session browser and full-text search. Once a session is selected you can browse and search within it, resume it or export to markdown. The MCP server provides tools to let Claude search back through the session for pre-compact context or pull from prior sessions. I use this constantly. I've seen elaborate continuity systems to give…
Jan 2026 · github.com
- 18
- 19RP
After some feedback I spent some time re-reading through the git docs, and refactored to add time tracking data into the commit message directly. It's simpler than using tags. thanks.
2025 · github.com
- 20PT
I've been trying to figure out how long feature development takes, for years. I'm not a fan of (a priori) estimations of work, which just seem like the wrong measure. I think I've got a better way. Genuinely interested if some git gurus can improve this. Particularly around the pre-push hook, which is dependent on retained squash commit text. Or if there's an entirely better way to achieve the same thing.
2025 · doocot.sh
- 21SA
Serie is a TUI application that uses the terminal emulators' image display protocol to render commit graphs like git log --graph --all. This is not a full-featured git client, nor are there any plans to add such functionality, so it is not a replacement for tig, lazygit, gitui, etc. The only purpose of this tool is to provide a pretty git log --graph and make commit information easily accessible. While some users prefer to use Git via CLI, they often rely on a GUI or feature-rich TUI to view commit logs. Others may find git log --graph sufficient. Personally, I found the output from git log…
Nov 2025 · github.com
- 22IC
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
- 23LA
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
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →