Git Workflows

Staging and committing

Stage all changes and commit with a descriptive message
Stage only the files in internal/api/ and commit
Write a commit message for my staged changes

BMO runs git add and git commit via the bash tool. You can ask it to follow any commit message convention:

Commit using conventional commits format (feat: / fix: / chore:)
Commit with a detailed body explaining why, not just what

Reviewing diffs

Show me what changed since the last commit
Summarize my changes as if writing a PR description
What files did I modify today?

BMO can run git diff, git log --oneline, and git status and then explain the output.

Creating branches

Create a new branch called feat/rate-limiting
Switch to the fix/auth-bug branch

Rebasing and merging

Rebase my branch onto main
Squash my last 3 commits into one

BMO will run the git commands but will ask for confirmation on destructive operations.

Auto-Checkpoint

Auto-Checkpoint automatically saves a git commit at regular intervals during a session. This provides a safety net without requiring you to ask for commits.

To enable:

[options]
auto_checkpoint = true
auto_checkpoint_interval = 5  # every 5 tool calls

Worktree isolation

For multi-agent workflows where parallel agents need isolated working trees, see Worktree Isolation.

Project initialization

On a new project:

/init

This creates the configured project context file (AGENTS.md by default) with project structure, build commands, and key context, making later git workflows aware of the project conventions.