Vibe Saver

Simple code management and GitHub backups. Vibe code with peace of mind.

Get Started View Source

Why Vibe Saver?

Simple Commands

Easy to remember commands that do exactly what you need

Never Lose Work

Stop worrying about code loss in Cursor or Windsurf

GitHub Backup

Seamlessly store your code in private GitHub repos

Cursor Compatible

Works perfectly with Cursor's AI features

Installation 

npm install -g vibe-saver

Add autocomplete:

vibe install

Then restart your editor or command line app.

Quick Start

  1. 1. Navigate to your project

    cd your-project

  2. 2. Initialize with Vibe Saver 

    vibe start

    This configures the current folder for vibe-saver to manage

  3. 3. Connect to GitHub Repository 

    vibe connect <repository_link>

    Your repository link should be in the format: https://github.com/username/repo.git

  4. 4. Save your work

    vibe save "Added new feature"

    Save your changes with a quick description so you never lose your progress.

  5. 5. Sync to GitHub

    vibe sync

    Pushes all your saved changes to the remote repository on GitHub.

Commands Reference

vibe start

Set up current folder for vibe-saver (git init)

vibe save <message>

Save your current vibes (git add + commit)

vibe connect <repository_link>

Connect to GitHub repository (git remote add)

vibe clone <url>

Grab code from GitHub (git clone)

vibe sync

Push your vibes to GitHub (git push)

vibe pull

Get latest vibes from GitHub (git pull)

vibe undo

Undo last vibe save & all unsaved changes (git reset --hard HEAD~1)

vibe clear

Clean up all changes since your last vibe save (git reset --hard HEAD)

vibe status

Check your current vibe status (git status)

vibe history

See your vibe history (git log)

vibe publish <tag>

Publish a stable vibe version for easy future reference (git tag)

vibe install

One-time setup to enable vibe-saver autocomplete in your terminal

Cursor Integration

Vibe Saver works perfectly with Cursor! Add these global rules to enhance your workflow & even have cursor help manage your code: 

# Vibe Saver Rules

When I mention vibe commands, understand these help you manage your code:
- `vibe save ` = Saves current changes (similar to git add + git commit)
- `vibe start` = Sets up current folder for vibe-saver (similar to git init)
- `vibe connect ` = Connects to GitHub repository (similar to git remote add)
- `vibe clone ` = Grabs code from GitHub (similar to git clone)
- `vibe sync` = Pushes changes to GitHub (similar to git push)
- `vibe pull` = Gets latest changes from GitHub (similar to git pull)
- `vibe undo` = Reverts last save and all unsaved changes (similar to git reset --hard HEAD~1)
- `vibe clear` = Cleans up all changes since last save (similar to git reset --hard HEAD)
- `vibe status` = Shows current state (similar to git status)
- `vibe history` = Shows commit history (similar to git log --oneline --decorate)
- `vibe publish ` = Publishes a stable version (similar to git tag + git push --tags)
- `vibe install` = Sets up shell completions for vibe commands

For common coding workflows, use appropriate vibe commands:
- After completing a feature: `vibe save "Add feature X"`
- Before ending work session: `vibe sync`
- When starting work: `vibe pull`
- When unsure of current state: `vibe status`