moshetanzer

quite cool! keep up the good work!

Yeah that is what we also figured. We are using https://forwardmyinbox.com which works quite well.

Ask HN,

It feels increasingly backwards that PR reviews are where we catch basic bugs, style issues, and convention violations.

With AI writing a large chunk of code now, the volume of small, avoidable mistakes has gone up. Yet we still wait until PRs to point out things that could have been flagged instantly, pre-commit, on the author’s machine.

PR review should be about design, correctness, and tradeoffs — not “missing await”, inconsistent patterns, or obvious slop.

Is there a good reason pre-commit review isn’t the norm, or are we just accepting an inefficient workflow because it’s familiar?

Curious how others see this.

https://commitguard.ai code reviews that are faster than linter that auto run pre commit and fully configurable.

Most code review happens at PR time, after code is already written, tested, and context is gone.

With more AI-written code, tests pass but logic issues still slip through. Would earlier, pre-commit code reviews make more sense?

I’m exploring this idea with a tool that reviews logic at commit time — curious how others think about timing reviews earlier.

Hey.

Linters are great for style and syntax, but logic errors still rely heavily on human review. Do you think a linter for code logic - for example: risky condition changes, missing error handling, inconsistent early returns, or unsafe null/undefined assumptions - would be useful in practice if it ran at lint-stage or commit time?

Curious to hear what would actually help

Hi HN,

I spent some time improving the CommitGuard landing page to make it clearer and more direct about what the tool does.

I’d love your honest feedback, does it make sense at a glance? Any suggestions for improvement?

https://commitguard.ai

Yip this won’t help them. Though I sure help there aren’t a lot of them ;)

i like the idea v nice

its not :)

I have found that PR based code reviews are two noisy and non configurable. Also unpredictable as to when they will run or if all is ok. Also it is never clear who’s problem it is (more like no one is intrested in dealing with it or it is just ignored totally)

So I created this tool that runs on commit. It is easily configurable and bypassable.

Would love to hear what community thoughts are on this idea.

You can also add custom prompts, choose context option and severity.