Alternatives
Products that do what GX CLI – Automatically stack large PRs to ship faster does
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…
- 1
- 2
- 3
- 4
- 5
- 6
- 7CC
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
- 8OS
Hey again HN. Isaac and I originally released a voice-first code review tool, but have since open-sourced it and turned it into just a better way to review your and your team's Github PRs. Main things we've heard that make code reviews slower are: 1) PRs are too big and overwhelming 2) Need to jump around to find the right context and relevant code 3) Need to spend time thinking (should not be a thing since AI exists), and writing comments What we built to address these: 1) PRs are split up into sub-PRs without needing to actually split them up and stack them yourself -> Automatically done…
2025 · github.com
- 9IM
2021 · 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
- 11AS
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
- 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
- 13BC
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
- 14DP
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
- 15NT
I built a CLI tool that turns codebases and PRs into diagrams so you can quickly understand how things fit together. Originally made it because I couldn't follow my own AI-generated repos. Just shipped a big update: - Switched from D2 to Mermaid for rendering - Tree-sitter AST parsing + agentic flow instead of raw LLM calls. ~50x faster. - Works on any GitHub repo or PR, not just local - Dropped the web frontend, it's just a CLI now - Published as a pip package Still a ton to improve and I'm building fast. Feedback, issues, PRs all welcome.
Feb 2026 · github.com
- 16ET
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…
Jan 2026 · github.com
- 17BA
2020 · github.com
- 18GA
2015 · github.com
- 19GT
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
- 20IB
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
- 21SG
Just wanted to clone a repo from my gh account and visualize it. Pretty easy with gitact. You can check any gh account. It’s called { gitact } quickly navigate through a user’s repos instantly grab the right git clone URL Feedback, stars and PRs are welcome
2025 · github.com
- 22RA
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
- 23AC
This week we released the Kodus CLI. It took a bit longer than we expected to ship. The reason was simple: there are already many ways to run reviews locally today. IDEs, extensions, terminal commands, agents inside the editor. So building “just another AI CLI” didn’t seem like a good idea. The question that guided the project was different: how can we bring the quality of PR reviews to the moment when the code is still being written? Today the CLI does two main things. The first is running local reviews using the same context we use in PRs. The goal was to avoid that shallow review that…
Mar 2026 · github.com
- 24IC
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
Ranked by how close each launch is in meaning, then by votes. Refine with a description →