Getting started

Git Vibe works best when you are moving quickly with AI-assisted development and still want each task to stay isolated.

Recommended tools

These are the tools that make the full Git Vibe workflow available:

• gh for issue-driven vibes, pull requests, and PR checks
• codex or code if you want git vibe open to launch a workspace app
• npx skills if you want to install the Git Vibe skill for Codex

Install Git Vibe

curl -fsSL https://raw.githubusercontent.com/sailscastshq/git-vibe/main/install.sh | bash

To pin a specific release:

curl -fsSL https://raw.githubusercontent.com/sailscastshq/git-vibe/v0.0.4/install.sh | GIT_VIBE_REF=v0.0.4 bash

If you are working from a local checkout, you can also run:

./install.sh

Install the skill too

If you use Codex, install the Git Vibe skill alongside the CLI. The CLI creates the worktree workflow. The skill gives the agent the conventions and commands to follow inside it.

npx skills add sailscastshq/git-vibe

What the installer sets up

The installer:

• installs git-vibe into ~/.git-vibe/bin
• installs global Git hook wrappers into ~/.git-vibe/hooks
• configures git vibe, git vc, and git vr aliases
• sets shared defaults such as vibe.baseBranch, vibe.branchPrefix, and vibe.worktreeRoot
• updates your shell profile so auto-jump works for git vibe code, git vibe enter, and git vibe finish

Reload your shell

The installer updates your shell profile, but it cannot modify the terminal session that launched it.

Open a new terminal or reload your profile:

source ~/.zshrc

git vibe ... works immediately through the Git alias. Reloading the shell is what enables direct git-vibe usage and the auto-jump shell integration in the current session.

Verify the install

git vibe version

Open your first vibe

From a clean main checkout:

git switch main
git pull --ff-only origin main
git vibe code fix-login-redirect

That creates:

• a branch like feat/fix-login-redirect
• a dedicated worktree under ../.vibe/<repo>/fix-login-redirect
• a context summary showing the path, compare target, and current change state

If you work from issues, you can start directly from the issue number:

git vibe issue 42

TIP

This is where the AI benefit becomes practical. Each vibe is isolated, so you can run one agent in one worktree, explore a second change in another, and keep main clean for review or release.

Attach AI context when you open a vibe

git vibe code --agent codex --task "fix login redirect" 42

This metadata makes it easier to resume a vibe later and understand what it was opened for.

Open a PR when you are ready

git vibe pr

Finish the vibe after merge

git vibe finish --sync 42

That fetches the latest remote state, verifies the merge, removes the worktree, and returns you to a clean main checkout.