[{"data":1,"prerenderedAt":74},["ShallowReactive",2],{"term-v\u002Fvibe-merge":3,"related-v\u002Fvibe-merge":59},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":53,"sitemap":54,"stem":57,"subcategory":6,"__hash__":58},"terms\u002Fterms\u002Fv\u002Fvibe-merge.md","Vibe Merge",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"A vibe merge is when you accept a merge without reading the diff because the vibes are right — tests pass, CI is green, the author is trustworthy. Efficient. Sometimes catastrophic when the vibes mislead you.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"A vibe merge describes approving or merging a PR with minimal review, relying on surface signals (passing CI, author reputation, PR size) rather than diff-level review. Common in high-trust teams and for bot PRs. Risk scales with change scope — small well-tested changes are safer to vibe-merge than large refactors.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"It's a Dependabot patch update — vibe merge it.\" \u002F \"That refactor is 2000 lines. Don't vibe merge.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"vibecoding","A vibe merge is when you accept a merge without reading the diff because the vibes are right — tests pass, CI is green, the author is trustworthy.","beginner","md","v",{},true,"\u002Fterms\u002Fv\u002Fvibe-merge",[49,50,51,52],"Code Review","Send It","LGTM","Ship It",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Fv\u002Fvibe-merge","rgAV_J3ER0tf629rPUtaRoyIgIYE20ypjfHBdhB0FYg",[60,64,68,71],{"title":49,"path":61,"acronym":6,"category":62,"difficulty":42,"description":63},"\u002Fterms\u002Fc\u002Fcode-review","general","A code review is when another developer reads your code before it gets merged, looking for bugs, bad practices, or anything confusing.",{"title":51,"path":65,"acronym":66,"category":40,"difficulty":42,"description":67},"\u002Fterms\u002Fl\u002Flgtm","Looks Good To Me","LGTM is the two-word code review approval that can mean anything from 'I carefully reviewed every line and this is perfect' to 'I glanced at the title and...",{"title":50,"path":69,"acronym":6,"category":40,"difficulty":42,"description":70},"\u002Fterms\u002Fs\u002Fsend-it","'Send it' is what you say right before pushing to production on a Friday afternoon. It's the deploy-culture equivalent of 'hold my beer.",{"title":52,"path":72,"acronym":6,"category":40,"difficulty":42,"description":73},"\u002Fterms\u002Fs\u002Fship-it","Ship it is the developer battle cry. It means 'this is good enough, let's deploy it.",1776518322534]