Alternatives
Products that do what CommitGuard does
AI-powered code review, right in your commits.
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10CA
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
- 11
- 12CR
Plannotator opens a local diff viewer (git, jj, p4). You annotate lines, tokens, or comment on files, and when you're done they feed straight into your agent session; creating an automated feedback loop. It works on local diffs, commits, branches, worktrees, and GitHub/GitLab PRs. The PR view lets you annotate the descriptions and comments while also being able to filter bot comments. The core tool enables focused manual review, the optional AI layer: - Ask AI: Ask questions directly inline - Guided Reviews: Have an agent reorganize a large diff into semantic overview sorted by…
Jul 2026 · plannotator.ai
- 13CT
2016 · commit.ws
- 14NT
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
- 15VL
I built a CLI that detects patterns AI coding tools leave behind: empty catch blocks, hardcoded secrets, as any everywhere, comments that restate the code, god functions, SQL concatenation. 24 rules across JS/TS and Python. Zero config, runs offline, regex-based so it's fast. npx @yuvrajangadsingh/vibecheck . Also ships as a GitHub Action for inline PR annotations and standalone binaries (no Node required). Why: CodeRabbit found AI-generated PRs have 1.7x more issues than human PRs. Veracode says 45% of AI code samples have security vulnerabilities. "Vibe coding" is everywhere now…
Mar 2026 · github.com
- 16WO
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
- 17IB
I’ve spent the last 2.5 months building a product that runs LLM-powered code reviews on my pull requests — and I just launched it. The tool is built specifically for solo developers. You install it on your repo, trigger a scan by creating a pull request, and it leaves structured review comments using OpenAI under the hood. Funnily enough, I used the dev version of this app to review its own pull requests while building it. It helped me spot bugs, simplify structure, and keep quality high — all with minimal need for another human in the loop. Things I want to try out in the next months : -…
2025 · codii.dev
- 18OS
Hey HN! I'm Hussam, a Senior Algorithm Engineer at CodiumAI. We launched PR Agent a little over a year ago — it’s a free and open-source tool that helps with reviewing pull requests. The response has been great and more than 70 contributors have added to the project. Today, we're launching PR Agent as a browser extension. Key features: - AI Chat in PRs: You can ask questions about specific code changes and the context is passed to the AI model - Automated Code Reviews: The /review command does an automated review, focusing on potential bugs, security issues, and best practice violations…
2024
- 19
Full visibility into your AI spend, before it goes rogue
25d ago · neatproxy.com
- 20AC
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
- 21CC
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
- 22
Instant CLI & Web to turn git diff into Conventional Commits
5d ago · ai-commit-tool.ikeda-lef.workers.dev
- 23BY
Hey HN - We're building wispbit (https://wispbit.com/) - a tool that lets you build your own AI code reviewer. We built this because we worked in big and complex codebases where we kept hitting booby traps - often the same ones. People forgot things, or quit altogether, amplifying the problem. We looked for other ways to fix this, but the solution is usually a combination of: - Writing a linter rule - too difficult and time consuming. - Writing docs and having frequent meetings on alignment - basically a full time job. - Using plug and play code reviewers - too generic and…
2025
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →