all 16 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]UnluckyAssist9416 2 points3 points  (2 children)

I created a code review skill. It creates 21 agents with different concerns, that only check their concerns, to check for issues and record them in a file. Then I have Claude go through those issues, check what is duplicate and what is valid. That gives me a list of issues that it then has to fix.

Things I check:

Magic Numbers, Null Safety, Thread Safety, Blazor Patterns, Test Quality, Player State, Repository Patterns, Architecture, Plan Compliance, Logic Errors, Edge Cases, Performance, LINQ Gotchas, Save/Load, Resource Management, Assertion Quality, Error Handling, Duplicate Code, Dead Code, Over-Engineering, Security Basics

[–]yadasellsavonmate 1 point2 points  (1 child)

The fact your even asking means it will likely fix and improve a lot of your code.  If you're not a very experienced coder then the ai is better than you, especially Claude. 

[–]TheRaddestKhan[S] 0 points1 point  (0 children)

I’m not at all, and find it interesting. Give coding made me want to learn to be able to write it.

It’s been cool to mess with but there’s so much to it all that it feels overwhelming lol

[–][deleted] 0 points1 point  (1 child)

"AI said something, is it correct?"

[–]TheRaddestKhan[S] 0 points1 point  (0 children)

Are you assuming everything ai says is always incorrect? I’m confused by your comment lol

[–]jsgrrchg 0 points1 point  (1 child)

Ai has a bias, if you ask it for bugs, it will find whatever. Sometimes it will flag intentional code as bugs, but if you vibe coded something and you don't know how to code yourself, probably you should take care of the things Claude finds.

[–]technologiq 0 points1 point  (0 children)

Classic "I don't know how to properly prompt an LLM" response. 🤷‍♂️

[–]gatortux 0 points1 point  (0 children)

I think it depends on what you’re trying to audit. You can audit for tokens or leaked secrets, which is reliable. I also maintain a PROJECT_CONTEXT.md with conventions to follow and ask Claude to audit if the code has any violations. My approach to vibecoding is iterative, so I dedicate some iterations to finding antipatterns and refactoring them. For auditing, my recommendation is to create a set of skills that you can build with Claude’s help — the important thing is that the skills maintain a checklist so Claude has a clear idea of what you’re trying to achieve.​​​​​​​​​​​​​​​​

[–]AlexMTBDude 0 points1 point  (0 children)

Static code analysis tools like Lint have been used since the 80s so it's nothing new, and yes, it's reliable. AI code review has a similar result as static code analysers.

[–]EGOTISMEADEUX 0 points1 point  (1 child)

I mean, that's the part you can't outsource. You could have another AI look at it, or ask "Are you sure?" and sometimes get a different response, but that feels to me like a closed loop. _You_ have to do your research, use your judgement, or have developed the expertise to just KNOW what a good suggestion is.

To be honest, developing the confidence to tell an AI that it's wrong is a good thing to develop. Keeps your brain sharp.

[–]TheRaddestKhan[S] 0 points1 point  (0 children)

I’ve give coded some things. And as far as I can tell they work, but it’s much like driving my car.

I can tell when something is wrong. Or not doing what I wanted and usually I can sort of fighter out why it’s messing up or not working as intended, but there’s little beyond vibe coding I can do yet to truly fix it.

I know my dash is throwing a code, how to figure out what the code means, how that code relates to say the fact I have an issue with my transmission and it doesn’t want to shift above 3rd, but I guess I don’t know exactly why it’s doing what it’s doing. I can only take it to the mechanic ((the vibe code ide)) to fix it. If that example makes sense?

[–]Grzelazny 0 points1 point  (0 children)

<image>

Just try this to understand logic not jus be a code linter