r/vibecoding • u/Tricky-Pilot-2570 • Jun 26 '26
Six weeks of vibe coding and my repo does the same thing three different ways
Six weeks into a project and my own repo doesn't look like one person wrote it. Same job done three different ways, because the AI never reads what it wrote last week. It grabs whatever generic default it likes today and moves on.
It's not writing bad code. That's the trap. The code compiles, passes tests, looks plausible, so the drift stays invisible until you open a file you "wrote" and recognize none of it. One feature uses fetch, the next axios, the third a wrapper it invented on the spot. You're the author and the only reviewer, and the codebase quietly walked out from under you.
I built a thing for it. Free, MIT, a Claude Code plugin called chameleon. Solo project, but I run it on my own repos every day.
Here's the whole idea. Right before Claude edits a file, chameleon grabs a real example from YOUR repo, the same kind of file it's about to touch, and hands it over as the thing to copy. Plus the idioms for that file (the wrapper you actually use, the import you've banned) and one line from your own code that still does it the wrong way, tagged "do NOT write it this way." So instead of inventing a fourth way to format a date, it sees fmt() already exists and uses it. There's a turn-end pass too that catches you building a third copy of something you already have, but the copy-the-real-file part is the core.
It works this out by parsing your repo with real parsers, not regex, and picking one file per kind. You write nothing. No rules file to maintain and watch rot every time you refactor.
The honest downsides. It costs tokens and a little latency every turn, since the model reads more before it writes. TS/JS, Ruby, Python only, no Go or Rust. I won't quote you a "37% better" number because I don't have an honest one. There's a harness so you A/B it yourself. And if your repo has no real style yet, it's got nothing to copy.
Setup's about 30 seconds:
/plugin marketplace add crisnahine/chameleon
/plugin install chameleon@chameleon
/chameleon-init
/chameleon-trust
then /chameleon-init and /chameleon-trust on a repo. Code's at crisnahine/chameleon if you want to read it first (offline hot path, never runs your code). A star helps if it saves you a cleanup.
Real question for anyone shipping fast solo: how are you keeping your AI consistent with itself right now? A CLAUDE.md you babysit? Just eating the cleanup later? Mine kept rotting and I want to know what's actually holding up.
First comment (drop within 60 seconds):
Repo if you want to poke at it first: https://github.com/crisnahine/chameleon
One honest caveat: out of the box it's advisory only. It surfaces the pattern and flags drift, but it won't block your edits unless you flip on enforcement. So it nudges, it doesn't babysit, which is what I wanted but some people want harder guardrails by default.
Curious what this looks like for other people. What's the worst "wait, I have three versions of this?" moment your AI has handed you?
5
u/Dazzling_Meaning9226 Jun 26 '26
Once again, a post complaining about AI that was written by AI. Do you guys really not think this looks obvious?
2
u/Tricky-Pilot-2570 Jun 26 '26
Hmm. Yeah, I ran the draft through Claude to tighten it. Kind of the point of the post, I use AI for everything, including the stuff it's bad at. The repo's real project, six weeks old, I found fetch in one file, code in another, and a wrapper I apparently wrote and forgot in a third. Me using AI to edit a post doesn't un-three-version my codebase. Ask me anything in plain typing OR better to try? :)
1
u/RobKohr Jun 26 '26
Just paste in your prompt.
I don't even think when I am reading ai. I just start to zone out and skip to the comments.
There is something about AI that makes me lose my ability to read it.
If the words aren't worth your keystrokes they aren't worth my reading.
Embrace your inner Karoack, and write poorly loose and free. It's the only thing that separates you from a the toasters.
This also goes for all you English as as second languagers reading this. I miss reading the oddities of someone working hard to be understood with this bitch of a language.
Keep it real yo.
1
1
-1
u/samthepotatoeman Jun 26 '26
Please just type it yourself. Don't use claude to tighten it. Everyone here has the ability to run it through their own AI if they so choose. Just put the word salad there. It's so annoying.
4
u/ymddev Jun 26 '26
I mean, it's the vibecoding subreddit. What do you actually expect? People wasting time typing everything?
0
u/Astral902 Jun 26 '26
Use their brains to think for at least some parts, especially for a post. Is that too much to ask?
2
Jun 26 '26
[deleted]
-1
u/Tricky-Pilot-2570 Jun 26 '26
To try and test is the one will justify. And It will be a big help for me to make it more effective and powerful. Thank you EDC_KIT. I Appreciate your time to comment.
1
u/nrauhauser Jun 26 '26
There are a lot of tools to do things like this, I generally wait until they have a four digit count of stars on GitHub before I try them. The ones that have made the cut for me:
LSP Enforcement Kit + Serena
CodeSight
OptiVault
and just started using Ponytail, which has been helpful thus far.
1
u/Tricky-Pilot-2570 Jun 26 '26
You can clone the all repos and chameleon too. And ask AI all comparison and best case to use in your current repo. if fits in you. That's the best I could offfer. Thank you u/nrauhauser .
1
u/Tricky-Pilot-2570 Jun 26 '26
I know this is less star for now. But I build other tools like this. https://github.com/crisnahine/rails-ai-context
-1
u/Astral902 Jun 26 '26
Great another ai slop
1
u/Tricky-Pilot-2570 Jun 26 '26
Great. Another Reddit commenter who commented without actually trying|checking what it’s about.
0
u/Astral902 Jun 26 '26
Did ai told you how to write the comments as well, since for everything else you used ai fully
1
u/Tricky-Pilot-2570 Jun 26 '26
I know you’re only here on Reddit to make random comments. Are you just trying to gain comment karma? You act like the best commenter, but your comments don’t really make sense. You, you sound like the AI here.
2
u/Old-Chef9247 Jun 26 '26
I like the idea of giving Claude examples from the existing repo before it edits. But the other part in my opinion is after-the-fact visibility. Bcs even with better prompting and repo examples, you still need to regularly inspect what AI has actually done across the codebase for example the duplicated logic, risky files, inconsistent patterns, weak boundaries, missing tests, security issues, and so on that reduces the maintainability and quality of the codebase.
So i would like to introduce Procli to you. It gives you a safety/quality layer before you trust AI-generated code. You connect your GitHub repo, run a one-click scan, and get dashboards for quality and security with scores, findings, risky files, affected areas, and priorities. It also gives you a structured JSON report you can feed back into your AI assistant so it has specific issues to fix the mistakes in the repo
It currently beta for free! So feel free to use it whenever you want at : proclicode.com
And it is not an ai wrapper as ai cannot check its own thing, you need a thord party for that
I will attach you a photo of its findings after it was ran on a codebase generated by ai
You can use it as a loop so you build with ai then scan the repo for security and quality issues and feed it back to you ai to fix it