Vibe coders should start vibe testing

I spent 5 years as a C++ engineer writing code in a traditional way. Then I discovered vibe coding with claude. In 3 weeks, I built more than I did in a year.

​As I added features, I came to some conclusions:

1) AI is amazing at generating features,

2)... but it's terrible at security.

3) And a prolific regression generator.

When you’re vibe coding, your changes aren't atomic. You’re swapping out entire structures/files just to make a button work.

​How many times have you added a new feature to realize that a previous one stopped working? I dislike testing (sorry for the test driven development gurus), but I was not going to create apps that would break unexpectedly or make the users information vulnerable...

If we’re going to vibe code, we need to Vibe Test. It might sound cheesy, but that's how the thought first came to me... I built Vultest because I wanted the same one-click magic for security that I had for features.

• ​It scans your vibe-heavy codebase using Opus 4.6.

• ​It identifies the hallucinations and vulnerabilities the AI introduced while you weren't looking.

• ​Most importantly: It doesn't just give you a list of chores. You click "Apply Fix" and it opens the PR for you.

This is the first version of it, I still have a long list of features I want to implement but Ive heard collecting feedback first is the right way to go.

It works for github repositories, if anyone want me to adapt it to other code hosting platform, please let me know, I will look into it :)