Skip to main content

​
Usage

vibe commit [options]

​
Description

Create a new commit from your staged changes. This captures your code changes along with any AI prompts that were used during development.

​
Options

​
-m, --message
string
required
The commit message describing your changes.
​
--no-prompts
boolean
Skip capturing AI prompts for this commit.
​
--author
string
Override the commit author (format: “Name <email>”).

​
Examples

​
Basic Commit

vibe commit -m "Add user authentication"

​
Commit with Multi-line Message

vibe commit -m "Add user authentication

- Implement login form
- Add JWT token handling
- Create auth middleware"

​
Commit Without AI Prompts

vibe commit -m "Update dependencies" --no-prompts

​
Workflow

1

Make Changes

Edit your code files
2

Stage Files

vibe add .
3

Commit

vibe commit -m "Your commit message"
4

Push

vibe push

​
Output

A successful commit shows: 
Creating commit...
✓ Captured 3 AI prompts
✓ Commit created: abc1234

[main abc1234] Add user authentication
 3 files changed, 127 insertions(+), 12 deletions(-)

Run 'vibe push' to sync with VibeHub.

​
What Gets Committed

ContentIncluded
Staged file changesYes
Commit messageYes
Author informationYes
TimestampYes
AI prompts (from Cursor, Claude, etc.)Yes (by default)

​
AI Prompt Capture

One of VibeHub’s unique features is capturing AI prompts alongside your commits. When you commit:
  1. VibeHub scans for recent AI conversations
  2. Prompts from supported editors are captured
  3. Prompts are linked to the commit

​
Supported AI Tools

  • Cursor
  • Claude
  • GitHub Copilot Chat
  • Other AI assistants
AI prompts help your team understand not just what changed, but why and how the code was developed.

​
Disabling Prompt Capture

If you don’t want to include AI prompts for a specific commit: 
vibe commit -m "Routine update" --no-prompts

​
Writing Good Commit Messages

Explain what the commit does and why.Good: Add password reset functionality with email verificationBad: Fix stuff
Write as if giving a command.Good: Add login validationBad: Added login validation
Aim for 50 characters or less for the first line. Add details in subsequent lines.
vibe commit -m "Add user authentication

- Implement JWT token generation
- Add login/logout endpoints
- Create auth middleware"
If applicable, reference issue numbers.
vibe commit -m "Fix login timeout issue (#42)"

​
Common Patterns

​
Feature Commit

vibe add src/features/auth/
vibe commit -m "Add user authentication feature

- Login and logout functionality
- Session management
- Password hashing with bcrypt"

​
Bug Fix

vibe add src/utils/validation.js
vibe commit -m "Fix email validation regex (#123)

The previous regex didn't handle plus signs in email addresses."

​
Refactoring

vibe add src/components/
vibe commit -m "Refactor Button component for better accessibility

- Add ARIA labels
- Improve keyboard navigation
- Extract shared styles"

​
Error Handling

​
Nothing to Commit

Error: Nothing to commit. Stage files with 'vibe add' first.
Solution: Stage files before committing: 
vibe add .
vibe commit -m "Your message"

​
Empty Commit Message

Error: Commit message cannot be empty.
Solution: Provide a message with -m: 
vibe commit -m "Add feature"

​
Not Initialized

Error: Not a VibeHub repository. Run 'vibe init' first.
Solution: Initialize VibeHub in your project: 
vibe init

​
Local vs Remote

vibe commit creates a commit locally. To sync with VibeHub, you must run vibe push.
# Create local commit
vibe commit -m "Add feature"

# Push to VibeHub
vibe push