openclaw / clawpatch

What is clawpatch?

Clawpatch is an AI-powered code review CLI that breaks your codebase into semantic feature slices, reviews each one using a provider like Codex or Grok, and tracks findings in a local state file. It goes beyond typical linting by understanding project structure -- monorepo workspaces, test suites, routes, and build targets -- so reviews feel contextual rather than mechanical. After review, you can triage findings, run targeted fixes, and revalidate that patches actually resolved the issue.

Why is it gaining traction?

The workflow is refreshingly explicit. Unlike bots that flood your PR with comments, clawpatch gives you a structured loop: map features, review in batches, report findings, then fix one at a time with validation commands running automatically. The multi-language support is unusually broad -- it understands Next.js routes, Laravel controllers, Go packages, Rust crates, Gradle projects, and more without configuration. The safety model also stands out: review never touches files, fix requires a specific finding ID, and the tool never commits or pushes on its own.

Who should use this?

Backend teams maintaining polyglot monorepos will get the most value -- especially if you're already using Codex CLI. Teams tired of generic AI review tools that ignore your project's conventions might find this more useful. Small projects with complex test matrices could use it to surface gaps the team keeps missing. It's probably not for teams wanting zero-configuration automation; the init-map-review-fix cycle requires buy-in.

Verdict

Clawpatch is a thoughtful take on AI-assisted review if you want structured, auditable findings over spray-and-pray comments. The 296 stars reflect early-stage interest, and the documentation is functional but sparse. The credibility score of 0.85% signals this is a niche tool from a small team -- worth trying in a side project before betting on it for critical code paths.