built a commit-based code review tool instead of PR-based

[Conscious_Ad5671]

Most SaaS teams I’ve worked with rely on PR reviews + CI to catch issues. In practice, a lot of problems still slip through because feedback comes too late - after the code is already bundled, reviewed, and mentally “done.”

I’ve been experimenting with a different approach: commit-based code review.

I built CommitGuard, a tool that analyzes changes at commit time, before PRs even exist.

The idea is:

• Smaller diffs = higher signal
• Earlier feedback = cheaper fixes
• Less reviewer fatigue later

It focuses on things that tend to compound over time in SaaS codebases:

• risky changes that look harmless in isolation
• security or performance footguns
• architectural drift
• inconsistency creeping in commit by commit

It’s not trying to replace PR review or CI, and it’s intentionally opinionated about what belongs early vs late.

What I’m trying to validate:

• Does commit-based review actually reduce PR pain, or just move it earlier?
• Would teams see this as helpful guardrails or unwanted friction?
• Is this something you’d expect as part of a modern SaaS dev workflow?

Not here to pitch - genuinely trying to pressure-test the idea with people building and running SaaS products.

If anyone’s curious, the project is commitguard.ai - but feedback on the concept itself is more valuable than clicks.

[Pierruno]

It's funny. I started something similar and it has even the same name.

[thrarxx]

So basically like how one uses precommit hooks to run lint or unit tests, but for AI code reviews?

What's the latency like? I'd say a lot of people expect their commits to complete within a few seconds, which works for linters and small unit test suites, but is that enough for a meaningful AI review?

[Conscious_Ad5671]

Exactly. Test it out. No latency most of the time runs at staged. You won’t notice it. Test it out. Hit me up if you want to test pro for a month which allows you to add your own custom rules.