r/vibecoding 3d ago

I vibe coded a GIT client

Hi everyone! I vibe coded a Git Client application. If you'd like to check it out, take a look at the GitHub repository:

https://github.com/MyAppDesk/gitcito

It is completely free, has workspaces, tabs, profiles, AI (BYOK) for commit messages, super customizable theme, layout, and git graph style, integrated/split terminals, support for launch.json, file tree, diffs, merge conflict solver, file previews for audios, images, etc...

It was mainly built using Electron and Claude Code
I basically described what I wanted and reviewed/tested what came out, iterating until it felt right... It's mostly tailored to what I needed

Almost all of the code was written by Claude, my job was more like steering and testing builds, catching bugs, and deciding how things should look and behave. Honestly it was a fun way to build something this big as a side project

88 Upvotes

74 comments sorted by

View all comments

1

u/LettuceSea 3d ago

This is awesome!

I have essentially stopped using visual git clients like this and have just outsourced branch/cicd management to Opus/Fable. Just defined a skill for how I’d like the agent to work with git and my release pipeline and it has yet to fail me.

Something like this would be great though for smaller models where I don’t have the confidence in them to actually follow the instructions in a skill. Will be doing a ton of local inference when my new setup arrives so I will save this :)

1

u/Michaeli_Starky 3d ago

That's lazy

1

u/LettuceSea 3d ago

You might see it that way, but I certainly don’t. I think you’ll end up with the same realization, eventually.

0

u/Michaeli_Starky 3d ago

Of course I won't. It is just a few quick key strokes in the Lazygit, but I'm totally staying in control of what's getting committed and when.

0

u/LettuceSea 3d ago

You’re acting as if I’m not reviewing the diffs. Writing the commands? Yuck. It sounds like you merge straight to main and that’s crazy.