Quick Start

Git Workflow

When to Use Git Actions

• You've completed a logical unit of work (feature, bugfix, refactoring)
• All tests pass successfully
• Build completes without issues

• You've made one or more commits
• You're ready for code review

Action Format

{"action": "git_commit", "message": "fix: Resolve auth timeout\n\nBead: bead-abc-123"}

Git Action Examples

{"action": "git_commit", "message": "feat: Add user authentication\n\nBead: bead-abc-123"}

{"action": "git_push"}

{"action": "test", "notes": "Running tests before commit"}

{"action": "git_commit", "message": "fix: Resolve authentication timeout issue\n\nBead: bead-abc-123"}

{"action": "git_push", "notes": "Pushing committed fix"}

{"action": "done", "reason": "Fixed auth timeout, committed and pushed"}

Commit Message Format

<type>: <summary>

<detailed description>

Bead: <bead-id>

• feat

  : New feature

• fix

  : Bug fix

• refactor

  : Code restructuring

• test

  : Adding or updating tests

• docs

  : Documentation changes

• chore

  : Maintenance tasks

Git Best Practices

1. Commit After Success: Only commit when tests pass and builds succeed
2. Atomic Commits: Each commit should represent one logical change
3. Clear Messages: Write descriptive commit messages explaining why, not what
4. Reference Beads: Always include bead ID in commits

Security Considerations

• Secret Detection: Commits are scanned for API keys, passwords, tokens
• Commits are automatically tagged with your bead ID and agent ID

CEO