pr-agent vs no-mistakes

Two of the top projects in Code review and testing, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.

33rd of 4 in Code review and testing

pr-agent

LLM pull request reviewer that comments via /review, /describe and /improve

#44th of 4 in Code review and testing

no-mistakes

Local git proxy that runs AI review, tests and lint before opening a PR

Verdict

pr-agent ranks higher, 63 to 60. Of the 3 score parts we measure for both, pr-agent leads on 1, no-mistakes on 1 and 1 is even.

  • Adoptionpr-agent leads by 24 points, 41 to 17: a wide gap.
  • FreshnessEven at 100.
  • MaintenanceWe do not score no-mistakes on this; pr-agent has 99.
  • Easy to runWe do not score no-mistakes on this; pr-agent has 33.
  • Agent-readyno-mistakes leads by 40 points, 70 to 30: a wide gap.

Pick pr-agent if you are

Teams wanting self-hosted AI pull request review in CI or on their git host

  • Supports GitHub, GitLab, Bitbucket, Azure DevOps and Gitea
  • Model-agnostic via LiteLLM: OpenAI, Claude, Gemini, Bedrock, Ollama and others

Pick no-mistakes if you are

Developers who want agent-checked branches before raising PRs

  • Runs in an isolated worktree, so your working directory is not disturbed
  • Works with claude, codex, grok, opencode, copilot, cursor and others, with ordered fallbacks
pr-agent vs no-mistakes: score parts and facts
What we comparepr-agentno-mistakes
Score parts, out of 100
Adoption41, known17, niche
Freshness100, active100, active
Maintenance99, healthyNot scored for this kind
Easy to run33, some setupNot scored for this kind
Agent-ready30, minimal70, partly
Facts from GitHub and the README
Stars13.4k8.8k
LicenseMIT (permissive)MIT (permissive)
Last commitOct 2026Oct 2026
Last releaseOct 2026Sep 2026
LanguagePythonGo
DockerYesNo
GPUNot neededNot stated
arm64 or Apple SiliconNot statedNot stated

pr-agent

PR-Agent runs as a GitHub Action, CLI, Docker image or webhook service and posts AI-generated descriptions, reviews, code suggestions and Q&A on pull requests. Each tool makes a single LLM call, and a compression strategy handles large diffs. It supports GitHub, GitLab, Bitbucket, Azure DevOps and Gitea, and any model reachable through LiteLLM.

Who it is for: Teams wanting self-hosted AI pull request review in CI or on their git host

Strengths

  • Supports GitHub, GitLab, Bitbucket, Azure DevOps and Gitea
  • Model-agnostic via LiteLLM: OpenAI, Claude, Gemini, Bedrock, Ollama and others
  • One LLM call per tool, about 30 seconds per command
  • Review behavior is configurable through a TOML settings file and JSON prompts

Weaknesses

  • Described as a community-maintained legacy project of Qodo
  • /help_docs is disabled since v0.36.1 over a credential-exposure issue
  • Needs your own LLM API key and per-provider setup
  • Docker images moved to pragent/pr-agent from 0.34.2, so pinned references break
  • no GPU
  • Docker + Compose
  • Needs LLM API key (e.g. OpenAI), Git provider token
  • Models: OpenAI GPT, Anthropic Claude, Google Gemini, DeepSeek, Mistral

no-mistakes

no-mistakes places a local git remote in front of your real one. Pushing to it creates a disposable worktree and runs a pipeline (review, test, docs, lint, push, PR, CI) driven by a coding agent CLI such as claude or codex. The branch is forwarded to the real remote only after every gate passes, and a PR is opened for you. Safe fixes are applied automatically; other findings wait for approval in a TUI.

Who it is for: Developers who want agent-checked branches before raising PRs

Strengths

  • Runs in an isolated worktree, so your working directory is not disturbed
  • Works with claude, codex, grok, opencode, copilot, cursor and others, with ordered fallbacks
  • Three entry points: git push, a TUI, or a /no-mistakes agent skill
  • Watches CI after the PR opens and auto-repairs failures

Weaknesses

  • Requires a runnable coding agent CLI configured for every gate
  • Agent calls spend API quota; RAM and cost figures are unknown
  • CI repairs may need another full review pass if revalidate_repairs is set
  • Auto PR creation and CI watching are documented only for configured push targets such as GitHub
  • Needs git, a coding agent CLI (claude, codex, opencode, etc.)
  • Models: claude, codex, grok, rovodev, opencode

More in Code review and testing

Building with these?

We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.