no-mistakes README

The project's README from github.com/kunchenguid/no-mistakes. As one markdown file: README.md.

git push no-mistakes

Release Platform X Discord

kunchenguid%2Fno-mistakes | Trendshift

Kill all the slop. Raise clean PR.

English · 简体中文

no-mistakes demo

no-mistakes puts a local git proxy in front of your real remote. Push to no-mistakes instead of origin, and it spins up a disposable worktree, runs an AI-driven validation pipeline, forwards the branch to the configured push target only after every check passes, and opens a clean PR automatically.

Full documentation: https://kunchenguid.github.io/no-mistakes/

How it works

        your branch
            │  git push no-mistakes
            ▼
   ┌────────────────────────────────────────────────┐
   │  disposable worktree — your work stays put     │
   │  review → test → docs → lint → push → PR → CI  │
   └────────────────────────────────────────────────┘
            │  every check green
            ▼
        clean PR, opened for you

Each step either passes on its own or stops with a finding for you to act on. Safe, mechanical fixes are applied automatically; anything that touches your intent is escalated for you to approve, fix, or skip. The initial change reaches the configured push target only after every local gate is green.

When CI itself fails, the pipeline repairs it and publishes that repair through the same guarded force-push path - but only when it can prove the repair builds on the head you already reviewed. When it cannot prove that, the repair goes back through Review before it is published, so unrelated history cannot replace the reviewed commit. Merge-conflict repairs rewrite history, so they always take that safer route. Set ci.revalidate_repairs: true if every CI repair must itself be reviewed, at the cost of another full pass over your change each time CI is repaired.

Install

curl -fsSL https://raw.githubusercontent.com/kunchenguid/no-mistakes/main/docs/install.sh | sh

Windows, Go install, and build-from-source instructions are in the installation guide.

Quick Start

$ no-mistakes init
  ✓ Gate initialized

    repo  /Users/you/src/my-repo
    gate  no-mistakes → /Users/you/.no-mistakes/repos/abc123def456.git
  remote  [email protected]:you/my-repo.git
   skill  /no-mistakes installed for agents at user level

  Push through the gate with:
  git push no-mistakes <branch>

$ git checkout my-branch

# do some work in the branch...

$ git push no-mistakes
  * Pipeline started

  Run no-mistakes to review.

$ no-mistakes
# opens the TUI for the active run

For GitHub fork contributions, keep origin pointed at the parent repository and initialize with no-mistakes init --fork-url <your-fork-url>.

From the TUI you act on each finding: auto-fix ones are applied for you (or approve to let them), ask-user ones are a judgement call you approve, fix, or skip. Once every check is green, the gate forwards your branch to the configured push target and opens the PR for you, so there is no manual git push origin and no hand-written PR body. Prefer to let your coding agent drive the same flow headlessly? Use /no-mistakes (see below).

Three ways to trigger the gate

Every change runs through the same pipeline. Pick the entry point that fits how you're working when the change is ready:

no-mistakes init installs the /no-mistakes skill for Claude Code and other agents. Under the hood the skill drives no-mistakes axi, a non-interactive TOON interface to the same approval flow.

See the quick start for the full first-run walkthrough.

Development

make build   # Build bin/no-mistakes with version info
make test    # Run go test -race ./... (excludes the e2e suite)
make e2e     # Run the tagged end-to-end agent journey suite
make e2e-record # Re-record e2e fixtures when agent wire formats change
make lint    # Check generated skill drift and run go vet ./...
make skill   # Regenerate committed no-mistakes skill files
make fmt     # Run gofmt -w .
make demo    # Regenerate demo.gif and demo.mp4 (needs vhs and ffmpeg)
make docs    # Build the Astro docs site in docs/dist

See Makefile for the full target list.

make e2e-record overwrites internal/e2e/fixtures/ from the real claude, codex, opencode, and antigravity CLIs, spends real API quota, and should be reviewed before committing.

Star History

Star History Chart

no-mistakes (kunchenguid/no-mistakes)

Searching Database…

8.9K ·GitHub
No-mistakes
What is this?A local git proxy that sits in front of your real git remote: you push to no-mistakes instead of origin, it spins up a disposable worktree, runs an AI-driven validation pipeline, and only forwards the branch to your real remote (opening a clean PR) once every check passes.
Is this a CLI tool or a hosted service?It is a local command-line tool and TUI written in Go that you run on your own machine; it acts as a git remote proxy rather than a hosted service.
How do I get it running?Run 'no-mistakes init' to install the gate and the /no-mistakes agent skill, then trigger the gate either by pushing a committed branch to the no-mistakes remote, running the no-mistakes TUI wizard, or invoking /no-mistakes from your coding agent.
Which coding agents can drive the validation pipeline?It is agent-agnostic: claude, codex, grok, rovodev, opencode, pi, copilot, antigravity, and cursor/acp via acpx are supported with ordered fallbacks, but every gate needs at least one runnable configured pipeline agent.
Does the gate block me while it checks my code?No, the pipeline runs in an isolated worktree so it does not disrupt your ongoing work, and findings that need judgement are escalated to you rather than auto-applied.
What are the three ways to trigger the gate?Push directly to the no-mistakes git remote, run the no-mistakes TUI wizard to branch/commit/push through the gate, or use the /no-mistakes agent skill to have your coding agent do a task and gate it.
What happens once every check passes?The gate forwards your branch to the configured push target and opens the PR for you automatically, so there's no manual git push to origin or hand-written PR body.
Who decides how findings get fixed?You do - auto-fix findings are applied for you (or after your approval), while ask-user findings are a judgement call you approve, fix, or skip from the TUI.
What is axi?no-mistakes axi is a non-interactive TOON interface to the same approval flow, used internally by the /no-mistakes skill to drive the pipeline headlessly.
What are similar projects?orca, superpowers-zh, gastown, brag, gentle-ai, testsprite-cli, github-mcp-server, pstack-claude
Which topics is it in?pull-request, copilot, antigravity, code-review, opencode, github, workflow-automation, tui, git, cursor, coding-agent, go
Creator
kunchenguid
Size
13.8 MB
Stars
8.9K
Updated
CommitOct 15Releasev1.84.0Sep 26
Age
6mo
Commits · 90 Days