We are all using AI to write code now. Whether it's Claude Code, Aider, or Copilot, the speed is incredible. But there is a glaring bottleneck we don't talk about enough: AI code is often just slightly broken. 🤖💥
It forgets an import, misses a type definition, or fails a test.
Usually, you only find out after you push to GitHub. Your CI/CD pipeline turns red 🔴, and you end up polluting your Git history with a dozen commits titled fix: linting
or fix: missing test variable
.
I recently found a repository called no-mistakes that solves this brilliantly. It acts as a local proxy between your terminal and GitHub, forcing AI to test and fix its own code before anyone else sees it.
Here is why it's worth a look. 👇
Right now, developers handle broken code in two ways:
Both methods are passive. They tell you something is broken, but they leave the cleanup to you. When you're using an AI coding agent to generate the code in the first place, manually babysitting its output defeats the purpose.
no-mistakes
no-mistakes
is a CLI tool that intercepts your git push
. Instead of sending your code straight to origin, it routes it through a localized validation pipeline.
The biggest differentiator is that it is active, not passive.
If a pre-commit hook fails, the process stops. If no-mistakes
fails, it initiates an agentic review loop. It uses an interactive Terminal UI (TUI) to show you exactly what the AI is trying to fix. If the AI gets stuck, you can step in and provide guidance right in the terminal.
It also integrates natively with tools like Claude Code. You can literally tell your agent, "Use the /no-mistakes skill to verify and gate these changes," and it will handle the entire lifecycle. 🤯
One command. Review, test, and validate
main
branch before testing, preventing hidden merge conflicts.README.md
to keep documentation from going stale.Setup takes about 30 seconds. ⚡
1. Install the CLI tool globally:
curl -fsSL https://raw.githubusercontent.com/kunchenguid/no-mistakes/main/docs/install.sh | sh
2. Initialize it in your project folder:
no-mistakes init
This wires up a new git remote proxy called no-mistakes
.
3. Change how you push:
The next time you (or your AI) finish a feature, skip git push origin
. Instead, run:
git push no-mistakes
The tool will take over, spin up the worktree, run your suites, fix the AI's slop, and open the PR for you. 🎉
As AI agents write more of our code, our tooling needs to shift from writing to verifying.
How are you currently handling AI-generated bugs in your workflow? Are you still manually running tests and fixing the AI's mistakes, or have you started automating the review loop? Let me know in the comments! 👇