Who no-mistakes is for#
Solo developers using agents
Use no-mistakes when an agent produces a branch and you want a structured local gate before publishing it.
Skip if:
You prefer to inspect and push every branch manually without local automation.
Small teams with noisy PRs
Teams can use it to catch formatting, generated-file, test, and PR-description issues before shared CI runs.
Skip if:
Your hosted CI already blocks every required check and PR quality is not a pain point.
Agent-native repositories
The /no-mistakes skill gives coding agents a defined way to finish work and submit it through a gate.
Skip if:
Your team forbids agents from creating commits or preparing PRs.
The problem it solves#
Agent-assisted coding can produce fast changes, but fast changes still need review discipline. Developers need a pre-push gate that runs checks, proposes safe fixes, escalates judgment calls, and opens a clean PR only after the branch is ready.
How it solves it#
Pre-remote Git gate
Developers push to a local no-mistakes remote first, and the branch is forwarded to the configured target only after the pipeline passes.
Disposable worktree validation
The pipeline runs in an isolated worktree, keeping the developer's current checkout available while review and fixes run.
Multiple workflow entry points
Teams can trigger the same gate through git push no-mistakes, the no-mistakes TUI, or the /no-mistakes agent skill.
Agent-agnostic execution
The README lists support for Claude, Codex, OpenCode, Copilot, ACP targets, and other agent interfaces.
Human judgment stays explicit
Safe fixes can be applied automatically, while findings that touch intent require the user to approve, fix, or skip.
Strengths and trade-offs#
Strengths
- Runs before hosted CIno-mistakes catches many issues before a branch reaches the real remote, reducing noisy PR churn.
- Works with existing agentsThe gate does not require one specific AI assistant, which makes it easier to adopt in mixed-agent teams.
- Local-first safety modelDisposable worktrees and explicit approvals give teams a clearer boundary between automation and developer intent.
Trade-offs
- -Adds a new Git habitDevelopers need to initialize the gate and push through no-mistakes instead of pushing directly to origin.
- -Pipeline quality depends on configurationThe gate is only as useful as the tests, lint checks, docs rules, and agent permissions configured for the repository.
- -Not a replacement for code reviewno-mistakes prepares cleaner PRs, but humans still need to review product intent, architecture, and risk.
no-mistakes vs alternatives#
Compared to GitHub Actions
GitHub Actions runs after code reaches GitHub, which makes it the right shared CI system for branch protection and team visibility. no-mistakes runs before forwarding a branch to the real remote, so it helps developers catch local quality issues, generate a cleaner PR, and reduce noisy CI churn. Most teams should treat no-mistakes as a pre-PR gate and keep GitHub Actions as the final shared enforcement layer.
What it's built on#
- Languages
- Go
FAQ#
What does no-mistakes do?
no-mistakes gates Git pushes through a local validation pipeline before forwarding the branch and opening a PR.
Does no-mistakes change my active checkout?
The README says the pipeline runs in a disposable worktree, so your active working tree stays available while checks run.
What license does no-mistakes use?
GitHub metadata reports no-mistakes as MIT licensed.
How do you install no-mistakes?
The README provides an install script and links to Windows, Go install, and build-from-source instructions in the installation guide.
Similar open-source tools#
VibePad
Control your AI coding assistant with a gamepad, open source
orca
The ultimate IDE for coding agents
agentmemory
Persistent memory for AI coding agents
Agent Skills
Structured workflows for AI coding agents.
Flue Framework
Build powerful, autonomous agents with TypeScript.
jcode
Next-gen coding agent harness for efficient workflows