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.

Last verified
Automate Git push review in a disposable worktree before opening a clean PR. MIT licensed with CLI, TUI, and agent skill entry points.
Use no-mistakes when an agent produces a branch and you want a structured local gate before publishing it.
You prefer to inspect and push every branch manually without local automation.
Teams can use it to catch formatting, generated-file, test, and PR-description issues before shared CI runs.
Your hosted CI already blocks every required check and PR quality is not a pain point.
The /no-mistakes skill gives coding agents a defined way to finish work and submit it through a gate.
Your team forbids agents from creating commits or preparing PRs.
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.
Developers push to a local no-mistakes remote first, and the branch is forwarded to the configured target only after the pipeline passes.
The pipeline runs in an isolated worktree, keeping the developer's current checkout available while review and fixes run.
Teams can trigger the same gate through git push no-mistakes, the no-mistakes TUI, or the /no-mistakes agent skill.
The README lists support for Claude, Codex, OpenCode, Copilot, ACP targets, and other agent interfaces.
Safe fixes can be applied automatically, while findings that touch intent require the user to approve, fix, or skip.
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.
no-mistakes gates Git pushes through a local validation pipeline before forwarding the branch and opening a PR.
The README says the pipeline runs in a disposable worktree, so your active working tree stays available while checks run.
GitHub metadata reports no-mistakes as MIT licensed.
The README provides an install script and links to Windows, Go install, and build-from-source instructions in the installation guide.
Alternative to
Fly.io
Zero-downtime Docker deploys to any server, no managed platform.
Alternative to
Heroku
Self-hosted PaaS: deploys any language, automatic HTTPS, zero fees.
Alternative to
Heroku
Self-hosted PaaS to deploy apps and databases across multiple servers
Alternative to
GitHub
Self-hosted Git forge for teams that want platform independence
Alternative to
GitHub
Git, CI/CD, issue tracking, wikis, and AI agents on your own server.
Self-hosted Spring Boot monitoring, no Prometheus or Grafana needed
Featured
Alternative toClaude Managed Agents
Open-source agent deployment API. Self-host or use Omnara Cloud.
Alternative to
Grok Bot
AI teammates you own: your keys, your model, your machine.
Alternative to
Superhuman
AI email assistant that drafts replies and clears your inbox
The projects we add and every new guide. Free, unsubscribe any time.