kunchenguid /no-mistakes

git push no-mistakes

★ 9,115⑂ 952👁 49▤ 206
More from this author
+0
Daily
+0
Weekly
+280
Monthly
9,115
stars
952
forks
49
watchers
–
prs
–
issues
206
releases

README

git push no-mistakes

  
  
  
  



  


Kill all the slop. Raise clean PR.

English · 简体中文


  


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.

- Non-blocking - the pipeline runs in an isolated worktree without disrupting your work.
- Agent-agnostic - claude, codex, grok, rovodev, opencode, pi, copilot, antigravity, or cursor / devin / acp: via acpx, with ordered fallbacks; every gate requires a runnable configured pipeline agent.
- Agent-native - /no-mistakes lets your coding agent do a task and gate it, or gate existing committed work: it runs the pipeline, has the pipeline apply safe fixes, and escalates the rest to you.
- Human stays in charge - auto-fix or review findings, your call.
- Clean PRs by default - push, open PR, watch CI, and auto-fix failures in one shot.

Full documentation: 

 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

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


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

 Quick Start

sh
$ 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 

$ 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 fo

Snapshot: 2026-11-04T14:00:00Z · Data license Apache-2.0 · JSON