A small and simplified set of commands for vibe coders to leverage version control without getting overwhelmed by the learning curve of git.
Help a new vibe coder out and tell them about us. Or try it for yourself on NPM. =)
Initially, I thought this would be funny, but then I saw all the posts on X and reddit about massive progress lost by a prompt gone awry. I thought about it some more and finally decided to build something.
I've used git myself for well over a decade, and I still remember watching YouTube videos and doing a codeschool course, trying to wrap my head around it in the beginning. If you're working solo on something, that's a big hurdle, especially when the other barriers to entry have gotten so low!
Then there's the fact of how many of us have aliases set up for git anyway. `gca` and `gcmsg "<message>"` save a lot of keystrokes. While I made this for newbs, I find myself actually using `vibe save "<message>"` unironically already.
A small and simplified set of commands for vibe coders to leverage version control without getting overwhelmed by the learning curve of git.
Help a new vibe coder out and tell them about us. Or try it for yourself on NPM. =)
Initially, I thought this would be funny, but then I saw all the posts on X and reddit about massive progress lost by a prompt gone awry. I thought about it some more and finally decided to build something.
I've used git myself for well over a decade, and I still remember watching YouTube videos and doing a codeschool course, trying to wrap my head around it in the beginning. If you're working solo on something, that's a big hurdle, especially when the other barriers to entry have gotten so low!
Then there's the fact of how many of us have aliases set up for git anyway. `gca` and `gcmsg "<message>"` save a lot of keystrokes. While I made this for newbs, I find myself actually using `vibe save "<message>"` unironically already.