dearilos

7 ms·

31.
Show HN: Wispbit – Keep codebase standards alive(wispbit.com)
3 points by dearilos 1y ago|0 comments
32.
Show HN: Open Source AI Code Review Agent for Teams(github.com)
2 points by dearilos 1y ago|0 comments
33.
by dearilos 1y ago
problem with the tools you're using is that they're not built for code review im building one that lets you write and enforce your own rules so you don't get the typical slop email in profile if you'd like to try it - i
34.
by dearilos 1y ago
i'm taking an approach where we scan your codebase and keep rules up to date you can enforce these rules in code review after CC finishes writing code email ilya (at) wispbit.com and ill send you a link to set this up
35.
by dearilos 1y ago
do you use anything today for automated code reviews?
36.
by dearilos 1y ago
ive been building out a directory of code review rules for the last couple of months! are you open to chatting and sharing notes on what works/doesn't work? my email is ilya (at) wispbit.com
37.
by dearilos 1y ago
I'm actually building something like this. A code review tool that can be ran by Claude Code (and other tools like cursor, kiro, windsurf) where it does the first pass. You can also define the rules on how code should be reviewed, and
38.
by dearilos 1y ago
Do you use any tools to help with the code review part?
39.
by dearilos 1y ago
How has that worked out so far? I'm building something similar and I found that code review with LLMs is really good when: - You give it specific rules. I built a directory for these because they made the reviewer so much better [1] -
40.
by dearilos 1y ago
AI coding agents help you solve the problem faster AI code review helps you catch issues you've forgotten about and eliminates the repetitive work These tools are helping developers create quality software - not replace them
41.
by dearilos 1y ago
how'd you get your code review automated?
42.
by dearilos 1y ago
There is so much slop that you end up ignoring the important stuff AI code review really does help but only when used correctly I'm building the tool to fix that
43.
by dearilos 1y ago
This is what sucks about code review today It's just slop and useless context Code review should only help with the repetitive and tedious parts of review I'm building a tool to fix that
44.
by dearilos 1y ago
if you do specific prompts based on your team's tribal knowledge and standards it works really well "look at this code for bugs" doesn't end up working well, which is what most code reviewers do.
45.
by dearilos 1y ago
how are you dealing with the accuracy of the review comments? in my experience "review this PR" is very generic and ends up giving slop.
46.
by dearilos 1y ago
There's a lot of arguments being made here that background agents aren't effective because code review is the bottleneck. I built a tool that understands the codebase and can give the agent the first pass. So you don't need t
47.
by dearilos 1y ago
I'm actually building something to fix this. The biggest bottleneck for background agents is code review. I'm building a tool that can give the first pass so the result of the background agent isn't garbage most of the time.
48.
Ask HN: How did you find your early adopters?
1 points by dearilos 1y ago|0 comments
49.
by dearilos 1y ago
I found that early and often code reviews can offset the reduction in productivity. A good code review process can fix this.
50.
Ask HN: How are you reviewing code if you are mandated to use AI?
2 points by dearilos 1y ago|0 comments
51.
by dearilos 1y ago
I'm thinking about this a little differently. You have to catch most issues at code review. You can have an agent spit out code, but on PR open you should have another agent verify rules based on rules you define as a team. It's w
52.
by dearilos 1y ago
I'm building a tool to do code reviews too. Are you open to trying it?
53.
by dearilos 1y ago
Gather all my acquired tribal knowledge and put it into a code reviewer [1] This way you're not asking juniors to fix every little thing and they can learn from standards that already exist. [1] https://wispbit.com
54.
by dearilos 1y ago
Agreed. Tribal knowledge and communication is the biggest bottleneck. As soon as your team starts growing, you spend most of your time in communication and not writing code. This is what I’m working on fixing at wispbit.com
55.
AI Code Review Rules Directory(wispbit.com)
3 points by dearilos 1y ago|0 comments
56.
How to fix your broken code review process(wispbit.com)
2 points by dearilos 1y ago|0 comments
57.
Show HN: Build your own AI code reviewer
8 points by dearilos 1y ago|0 comments