vibe add

Usage

vibe add [files...] [options]

Description

Stage files to be included in your next commit. Similar to git add, this command marks files as ready to be committed.

Arguments

files

string[]

One or more file paths to stage. Use . to stage all changes.

Options

--all

boolean

Stage all modified and new files. Shorthand: -A

--verbose

boolean

Show detailed output of staged files. Shorthand: -v

Examples

Stage a Single File

vibe add src/app.js

Stage Multiple Files

vibe add src/app.js src/utils.js README.md

Stage All Changes

vibe add .

Or:

vibe add --all

Stage with Verbose Output

vibe add . --verbose

Output

Basic Output

✓ Staged 3 files for commit

Verbose Output

Staging files...
  + src/app.js (modified)
  + src/utils.js (new file)
  + README.md (modified)

✓ Staged 3 files for commit

File States

State	Description
new file	File is being tracked for the first time
modified	Existing file has changes
deleted	File has been removed
renamed	File has been moved or renamed

Workflow

A typical workflow using vibe add:

# 1. Make changes to your code
vim src/app.js

# 2. Check what's changed
vibe status

# 3. Stage specific files
vibe add src/app.js

# 4. Or stage everything
vibe add .

# 5. Commit the staged changes
vibe commit -m "Add new feature"

# 6. Push to VibeHub
vibe push

Staging vs Committing

vibe add only stages files locally. You must run vibe commit to create a commit, then vibe push to sync with VibeHub.

Command	What It Does
`vibe add`	Stages files for the next commit
`vibe commit`	Creates a commit from staged files
`vibe push`	Pushes commits to VibeHub

Unstaging Files

To unstage files before committing:

vibe reset src/app.js

Or unstage all:

vibe reset

Ignoring Files

Files listed in .gitignore or .vibeignore will be excluded from staging. Common patterns to ignore:

# .vibeignore
node_modules/
.env
*.log
dist/
.DS_Store

Best Practices

Stage Related Changes Together

Group related changes in a single commit. Don’t mix unrelated changes.

# Good: Stage related auth files
vibe add src/auth.js src/login.js tests/auth.test.js
vibe commit -m "Add user authentication"

Review Before Staging

Check what you’re about to stage:

vibe status
vibe add src/app.js

Use Verbose Mode

When staging many files, use verbose mode to see what’s included:

vibe add . --verbose

vibe commit - Commit staged changes
vibe status - See what’s staged and unstaged
vibe push - Push commits to VibeHub

Getting Started

Commands

Usage

Description

Arguments

Options

Examples

Stage a Single File

Stage Multiple Files

Stage All Changes

Stage with Verbose Output

Output

Basic Output

Verbose Output

File States

Workflow

Staging vs Committing

Unstaging Files

Ignoring Files

Best Practices

Getting Started

Commands

​Usage

​Description

​Arguments

​Options

​Examples

​Stage a Single File

​Stage Multiple Files

​Stage All Changes

​Stage with Verbose Output

​Output

​Basic Output

​Verbose Output

​File States

​Workflow

​Staging vs Committing

​Unstaging Files

​Ignoring Files

​Best Practices

​Related Commands

Usage

Description

Arguments

Options

Examples

Stage a Single File

Stage Multiple Files

Stage All Changes

Stage with Verbose Output

Output

Basic Output

Verbose Output

File States

Workflow

Staging vs Committing

Unstaging Files

Ignoring Files

Best Practices

Related Commands