Skip to main content

Usage

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

Commit with Multi-line Message

Commit Without AI Prompts

Workflow

1

Make Changes

Edit your code files
2

Stage Files

3

Commit

4

Push

Output

A successful commit shows:

What Gets Committed

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:

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.
If applicable, reference issue numbers.

Common Patterns

Feature Commit

Bug Fix

Refactoring

Error Handling

Nothing to Commit

Solution: Stage files before committing:

Empty Commit Message

Solution: Provide a message with -m:

Not Initialized

Solution: Initialize VibeHub in your project:

Local vs Remote

vibe commit creates a commit locally. To sync with VibeHub, you must run vibe push.