no-mistakes adds AI validation layer before git push
`no-mistakes` is a local git proxy that intercepts pushes, runs a coding agent as a validation pipeline in a disposable worktree, and only forwards to the real remote after all checks pass.
Score breakdown
Developers using AI coding agents can use `no-mistakes` to automatically gate AI-generated code behind an agent-driven validation pipeline before it ever reaches their remote, reducing the risk of shipping low-quality or broken changes.
- 01Acts as a local git proxy sitting in front of the real remote, replacing direct pushes to `origin`.
- 02Spins up a disposable worktree for each push to isolate validation.
- 03Runs a coding agent as a validation pipeline before forwarding code upstream.
`no-mistakes` is a local git proxy designed to act as a quality gate before code reaches a real remote. The author, akane8, describes it as a way to eliminate "AI slop" — low-quality or unreviewed AI-generated code — by intercepting pushes before they reach `origin`.
When a developer pushes to `no-mistakes` instead of their actual remote, the tool spins up a disposable worktree and runs a coding agent as a validation pipeline.
When a developer pushes to `no-mistakes` instead of their actual remote, the tool spins up a disposable worktree and runs a coding agent as a validation pipeline. Only after every check in that pipeline passes does it forward the commit upstream. Beyond validation, it also automates opening a clean PR and babysits the CI pipeline, reducing manual follow-up work after a push.
Key facts
- 01Acts as a local git proxy sitting in front of the real remote, replacing direct pushes to `origin`.
- 02Spins up a disposable worktree for each push to isolate validation.
- 03Runs a coding agent as a validation pipeline before forwarding code upstream.
- 04Only forwards the push to the real remote after every check passes.
- 05Automatically opens a clean PR after a successful push.
- 06Monitors the CI pipeline on the developer's behalf after the push.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Apr 21, 2026 · 18:16 UTC. How this works →