Alternatives
Products that do what Enforcing time-bounded technical debt with Git history does
I kept running into the same problem in large codebases: “temporary” code almost never gets removed. People add TODOs, FIXMEs, or quick hacks to hit a deadline, and six months later nobody remembers why they’re there or who owns them. They quietly turn into production bugs. I built a small CLI that treats those comments as time-bounded instead of permanent. You can attach an expiry date to a TODO in the code, and when the date passes, CI fails and points to exactly where the expired code lives. It works by: scanning comments across any language parsing structured annotations and optionally…
- 1
- 2
- 3
- 4
- 5IC
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
- 6GC
2016 · github.com
- 7BP
I put together a small prototype that might help folks like me who struggle with keeping their website’s blog active just for SEO. It’s a basic tool: you enter your Git repo details (owner, name, branch), pick a date range, and it generates a short blog post from the commits in that period. The idea is to give small businesses and solo devs a way to keep their blog up-to-date with actual product updates without needing to write new content. Right now, it’s still pretty minimal but I’d really appreciate any feedback, especially if you think this could be useful, or if you have ideas on how it…
2024 · git2blog.streamlit.app
- 8GC
We built a Git-native CLI tool that automates Git branch stacking. Here's why stacking matters and how GX helps: Code review is a notorious bottleneck. You write a large PR, wait for review, get feedback, iterate, and wait again - especially painful across timezones. Meanwhile, you're blocked from shipping dependent changes. Stacking lets you parallelise development and code review by breaking changes into logical and dependent chunks. Current stacking tools will consider each commit its own PR, but GX will automatically group commits into separate stacks while optimising for structural…
2025 · github.com
- 9AF
2019 · github.com
- 10CC
We're two engineers that got fed up with context switching. Why do we need to do a git push, open a browser tab, wait for some task to actually start, bite nails (or read HackerNews) for 10 minutes or more while dependencies are being installed for the 100th time and finally end up with an invalid YAML error. And for some reason this usually happens in the final stage of the pipeline leading up to the inevitable git commits "Fixed", "Fixed again", "Test", "Really fixed this time". We can do better. We set out to build Zippy. A CI/CD system that works from your terminal. No context…
Mar 2026 · zippy.sh
- 11CC
Uses agent and Git Hooks to automatically create Git Notes on commit, containing the agent conversation that led to that commit. Works if either you or the agent commit. It's basically the same thing as entire.io just announced that they got $60m investment for. Except I got Claude Code to write it last week, in my spare time, without really paying attention. I certainly didn't read or write any of the code, except for one rubbish joke in the README. I've got a Claude Code instance working on Gemini CLI support and OpenCode support currently.
Feb 2026 · github.com
- 12PM
I built an MCP server that gives Claude Code long-term memory across sessions, backed by infrastructure you control. Every Claude Code session starts from zero, no memory of previous sessions. This server uses mem0ai as a library and exposes 11 MCP tools for storing, searching, and managing memories. Qdrant handles vector storage, Ollama runs embeddings locally (bge-m3), and Neo4j optionally builds a knowledge graph. Some engineering details HN might find interesting: - Zero-config auth: auto-reads Claude Code's OAT token from ~/.claude/.credentials.json, detects token type (OAT vs…
Feb 2026 · github.com
- 13CC
My team uses Claude Code daily, and the sessions have become some of the most useful artifacts we produce. But they're trapped in ~/.claude/projects/ on whichever laptop they happened on. There's no good way to hand a colleague "the session where I untangled the migration" so they can claude --resume it and keep going from where I left off. Enter ccgs: Share Claude Code sessions through an orphan branch (@ccgs/) in your existing repo's remote - Session files carry the author's absolute paths. On pull, ccgs rewrites the working dir back to your path so resume actually…
Jun 2026 · github.com
- 14BC
Hey HN, I'm Fedor (solo founder). After ~20 years of watching devs fight Git, I'm building Branching. Branching streams your local edits to teammates in real time - no manual push/pull. It's Git-compatible and works offline. Why you might care - Teams see each other's changes instantly instead of in PR-sized batches - Conflicts surface ASAP while context is fresh (LLM-assisted merge is experimental, off by default) - Same GitHub remote, so no migration Ships today - VSCode extension + desktop app (macOS / Windows / Linux) - 3 small product teams have been using it for 1–6…
2025 · branching.app
- 15AS
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
- 16AA
Hi HN. Live-Memory is an open-source Claude Code plugin / MCP server that serves as an always up-to-date memory of your codebase. It uses a separate, low-cost, large-context-window model to distill your repo's organization, conventions and general structure. It observes the primary agent's activity and builds an understanding of your repo passively over time. This way, when you start a new Claude Code session, your primary agent queries Live-Memory via one read-only ask_live_memory tool and bootstraps its understanding of the codebase for the particular task at hand, instead of…
Jul 2026 · github.com
- 17RP
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
- 18CA
Hello HN! I built a pre-commit code scanner that checks your staged changes for security vulnerabilities every time you run 'git commit'. I am an inexperienced programmer and this is my first personal project. Any feedback, positive or negative, big or small, relevant or not, would be greatly helpful and appreciated! The tool requires Gitleaks and Python to run, you will also need to use your own AI API key, which I understand is a big setup friction. You can check out my demo video instead if that is more convenient: https://youtu.be/ZYe5vWFRTus?si=9Fv8DhTHktwDK4mV Thank you…
Jun 2026 · github.com
- 19RA
I really like interactive rebases in Git, but always thought they took too much time and effort. There are tools that make them a lot nicer, like magit or GitUp, but they still ask a lot of you. So over the last two years I built Retcon. In the app, you can manipulate history directly (e.g. drag a commit to a different spot) at all times; even when there’s a conflict waiting for resolution, you can always keep making changes. You're not asked to first make a rebase TODO and then commit to it. So you no longer need to think too much ahead: you just make the changes you have in mind, see what…
2024 · retcon.app
- 20GL
2020 · github.com
- 21GR
I started an experiment to let a WASM-powered webapp interact with a local git repo and see how well this works. It turns out, it works pretty well! I made it into a "git wrapped" tool that shows you when you committed the most, and what languages and files you most touched. Despite the scary prompt when you use the filesystem API everything happens locally and your code stays private. (You can of course also just try it on cloned public github repos). Let me know what you think!
Dec 2025 · gitrewind.dev
- 22LA
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
- 23IB
I finally got fed up with making work + personal Git repos work on my machine. Ever clone a work repository and accidentally make commits using your personal email? Or forget how to make your work repos use your work SSH key? Yeah... same. So I built the tool I've always wanted. GitPersona - a CLI tool for managing many git profiles on a single machine. Shoutout to my boy Codex for helping me finally ship this.
Mar 2026 · github.com
- 24RA
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
Ranked by how close each launch is in meaning, then by votes. Refine with a description →