Yeah, you're not my intended audience, because you actually know what a linter is, that there are automated tools (aren't things like gofmt, clang-format and standard sweet?) and I'd guess that you've been using these for years.

I also think that if you're working interactively with Claude, it's of less use because you're keeping a lot of control and you probably review what it's doing. Plus you probably already have those terminal windows open where you just type the command and woop.

Things get murkier when you goose your way from zero to hero, which is something that's being heavily promoted as "anyone can code", right now. That's more the audience that in my opinion needs a tool like this. Environments like that rely heavily on MCP and the people that use it are often completely illiterate in the code that's being spat out.

I don't want to go through the trouble of teaching people command line. I have plenty experience with people just not capable of learning to use a simple interactive tool like git rebase -i origin/master and changing pick into fixup in the past. It's overwhelming. Running pylint and actually solving issues is worse to teach to someone that has no idea what they're doing: one may even have to look up what W0703 is and how to solve it. Barriers, barriers, barriers.

I could wish for only experienced contributors, but I think that I'd be making a mistake. Even if all LLM development stops today, vibe coding is not going away; I'd rather try to relieve some pain.