Comment by sailorganymede
19 hours ago
Honestly I love to see people working on this problem ! I actually built a similar project myself (https://github.com/bhurghundii/vibecheck.dev) except it prevents you from merging on the PR level. I’d love to get in touch to talk about it sometimes.
Edit: I see there are a lot of people questioning the value of this. The thing is that there are teams where people are just pumping tons of AI code without understanding their work (literally take the ticket and dump it) and shipping it. culture change is the right answer but v hard but this at least slows things down and is quick to implement
I also experienced pushback when I shared a similar skill with some of my colleagues (and it didn't mention "vibe" in the name). The main objection was "I am doing careful planning upfront, so I have the same level of understanding of the code as before".
Maybe they do. In my experience, the agent was going over the scenarios that I failed to consider during the planning stage, and it was net positive. I haven't tried it with a spec-driven approach.
I get what they say but what I see or have seen is totally different. I come from an engineering culture where we got AI token leaderboards and mandates to use AI for every single step of the development process. We started running into bad bugs recently due to people just copy pasting the Jira into the prompt so I feel there is space to put some intentionality in the areas which matter.
Does it check if the answers are AI generated?
Not yet. But you’re like the 5th person to mention it so I think I’ll add that feature. There are some AI prevention stuff like you can’t copy paste which means you gotta use the visualisation.