Alternatives
Products that do what GitHub does
Open source AI code review agent for teams
- 1WL
Hey HN! Ilya and Nikita here. We're building wispbit (https://wispbit.com) - a tool that helps keep codebase standards alive. With the help of AI coding tools, engineers are writing more code than ever. Code output has increased, but the tooling to manage this hasn't improved. Background agents still write bad code, and your IDE still writes slop without the right context. So we built wispbit. It works by scanning your codebase for patterns you already use, and coming up with rules. Rules are kept up to date as standards change, and you can edit rules any time. You can enforce…
Oct 2025 · wispbit.com
- 2IB
https://the-pocket.github.io/Tutorial-Codebase-Knowledge/
2025 · github.com
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12GB
Feb 2026 · blog.rbby.dev
- 13
- 14
- 15BY
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
- 16GF
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
- 17
- 18
- 19
- 20AO
I'm working on a coding agent for building iOS apps. It's built on openspec and xcodebuildmcp. It's free and open source.
Apr 2026 · github.com
- 21WB
Hey HN, We’re two developers (co-founders) with a team of 20 who got tired of spending hours reviewing PRs, so we built Infinitcode.ai, an AI-powered code reviewer that: - *Summarizes PRs in plain English*: No more deciphering 1,000-line diff jungles - *Catches more than bugs*: Security holes, performance pitfalls, code smells, even typos (yes, we’ll flag “vurnerabilities” and vulnerabilities) - *Zero onboarding*: Works instantly—no “let me learn your codebase for weeks” nonsense. Why we’re posting: We’re in alpha and need brutal honesty. Roast our tool, mock our UI, or tell us why AI will…
2025 · infinitcode.ai
- 22CS
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
- 23OS
Hey HN! I'm one of the cofounders of Sourcebot, an open source alternative to Sourcegraph. Sourcebot lets you index thousands of repos across multiple platforms (GitHub, GitLab, Bitbucket), and gives you a powerful interface to search across them. You can learn more in our original HN launch post: https://news.ycombinator.com/item?id=41711032 We just added an AI code review agent that reviews your PRs and automatically detects issues that a human reviewer may have missed. We've been using an AI code review agent for a few weeks now, and it regularly catches issues that we…
2025 · docs.sourcebot.dev
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →