Alternatives
Products that do what What % of your commits were written by AI? does
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!
- 1
- 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
- 3
- 4PM
I built a lightweight project management workflow to keep AI-driven development organized. The problem was that context kept disappearing between tasks. With multiple Claude agents running in parallel, I’d lose track of specs, dependencies, and history. External PM tools didn’t help because syncing them with repos always created friction. The solution was to treat GitHub Issues as the database. The "system" is ~50 bash scripts and markdown configs that: - Brainstorm with you to create a markdown PRD, spins up an epic, and decomposes it into tasks and syncs them with GitHub issues - Track…
2025 · github.com
- 5
- 6GF
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
May 2026 · github.com
- 7
- 8HW
A bunch of companies that I spoke to had their own claude & codex OTel dashboards that showed spend + seats per month. However, none of the dashboards actually analyzed how the engineers worked with the tools and if there were any areas for improvement! That's why I created https://www.promptster.ai. Managers get aggregate level view of code quality and how that ties with team workflows (nothing on a per-engineer level). While engineers get personalized coaching on how they can save tokens while keeping output high. We also have a tool built for individuals to test their local…
Jul 2026
- 9
Spotify Wrapped for Claude, Codex & a Public leaderboard.
Jun 2026 · whoburnedmore.com
- 10IC
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
- 11
I have been pushing up to 90 commits a day on a MacBook Air via 4-5 parallel agents. As you can imagine when all the agents try to build, test and run dev servers on an 8GB machine it is the fast lane to a force quit and restart. I also did not want to pay the CI minutes on 90 pushes a day. So I designed a local merge queue to have all commits land one at a time and fully tested. Hopefully this helps other folks with more modest machines. Appreciate any feedback.
Jul 2026 · github.com
- 12CS
We now write most of our code with agents. For a while, PRs piled up, causing review fatigue, and we had this sinking feeling that standards were slipping. Consistency is tough at this volume. I’m sharing the solution we found, which has become our main product. Continue (https://docs.continue.dev) runs AI checks on every PR. Each check is a source-controlled markdown file in `.continue/checks/` that shows up as a GitHub status check. They run as full agents, not just reading the diff, but able to read/write files, run bash commands, and use a browser. If it finds…
Feb 2026 · docs.continue.dev
- 13SS
Hola HN! Long time lurker, sometimes commentor, first time poster here. I’ve been working alongside my two co-founders and a few colleagues on a project I’m excited (and a little nervous) to share with you all! Like many of us, I’ve lived a tortured existence with AI coding (is it vibes?) over the past few months - I think November was a big moment with this. But, one thing I’ve noticed after building orchestration layer after orchestration layer is that the thing I always came back to was “what the hell is Claude Code actually doing?” Perhaps it’s because of the time Claude Code got…
Jun 2026 · backplanes.com
- 14DI
For the past 4 years, I've been tracking the install counts of AI coding extensions in the Visual Studio Code marketplace (GitHub Copilot, Claude Code, OpenAI Codex, etc.) Today, I built an interactive dashboard that lets you see daily install counts for any of them over time. The chart shows GitHub Copilot by default, and you can overlay or swap in any of the other 20+ tools to compare. You can also see important dates in each tool's history (pricing changes, major releases, etc.) and how daily installs changed around those dates. Important caveats: 1) This only tracks VS Code extension…
Oct 2025 · bloomberry.com
- 15
- 16AS
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
- 17CC
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
- 18AL
Feb 2026 · claude-commits.vercel.app
- 19
- 20
- 21SP
Hey HN, My cofounder and I have gotten tired of CC ignoring our markdown files so we spent 4 days and built a plugin that automatically steers CC based on our previous sessions. The problem is usually post plan-mode. What we've tried: Heavily use plan mode (works great) CLAUDE.md, AGENTS.md, MEMORY.md Local context folder (upkeep is a pain) Cursor rules (for Cursor) claude-mem (OSS) -> does session continuity, not steering We use fusion search to find your CC steering corrections. - user prompt embeddings + bm25 - correction embeddings + bm25 - time decay - target query embeddings -…
Mar 2026 · gopeek.ai
- 22
- 23
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 24FF
It uses your local Claude and GitHub CLI and git worktrees, so there's nothing to configure beyond what you already have. Our AI coding workflow was a hodgepodge of scripts and ad-hoc processes, so we built this to centralize and streamline - and most importantly adapt as things change. Some cool features so far (lots more planned): 1. One click github issue to agent working on it. 2. Ratcheting mode, where it watches CI for code review comments and build failures, and automatically fixes them. Would love genuine feedback, bug reports, PRs, suggestions, etc.
Feb 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →