Git Workflow Patterns | Google Antigravity Directory

.antigravity

# Git Workflow Patterns for Google Antigravity

Master effective Git workflows for seamless team collaboration with Google Antigravity IDE.

## Branch Naming Conventions

```bash
# Feature branches
feature/user-authentication
feature/add-payment-integration
feature/JIRA-123-update-dashboard

# Bug fix branches
fix/login-redirect-issue
fix/JIRA-456-null-pointer-error
hotfix/critical-security-patch

# Other branch types
release/v2.1.0
docs/api-documentation
refactor/database-queries
test/integration-tests
```

## Commit Message Format

```bash
# Conventional Commits format
<type>(<scope>): <description>

[optional body]

[optional footer(s)]

# Types
feat:     New feature
fix:      Bug fix
docs:     Documentation only
style:    Formatting, missing semi-colons
refactor: Code change that neither fixes nor adds
perf:     Performance improvement
test:     Adding missing tests
chore:    Build process or auxiliary tools
ci:       CI configuration files

# Examples
feat(auth): add Google OAuth integration

- Configure OAuth client
- Add callback handler
- Store tokens securely

Closes #123

fix(api): resolve race condition in user creation

The user creation endpoint could create duplicate users
when requests arrived simultaneously. Added database
locking to prevent this.

Fixes #456
```

## Git Hooks with Husky

```typescript
// package.json
{
  "scripts": {
    "prepare": "husky install",
    "lint": "eslint . --ext .ts,.tsx",
    "format": "prettier --write .",
    "test": "vitest run",
    "typecheck": "tsc --noEmit"
  },
  "lint-staged": {
    "*.{ts,tsx}": [
      "eslint --fix",
      "prettier --write"
    ],
    "*.{json,md}": [
      "prettier --write"
    ]
  }
}

// .husky/pre-commit
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

npx lint-staged

// .husky/commit-msg
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

npx --no -- commitlint --edit $1

// commitlint.config.js
module.exports = {
  extends: ["@commitlint/config-conventional"],
  rules: {
    "type-enum": [
      2,
      "always",
      ["feat", "fix", "docs", "style", "refactor", "perf", "test", "chore", "ci"]
    ],
    "subject-case": [2, "always", "lower-case"],
    "subject-max-length": [2, "always", 72]
  }
};
```

## PR Template

```markdown
<!-- .github/pull_request_template.md -->
## Description
Brief description of changes

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Documentation update

## How Has This Been Tested?
- [ ] Unit tests
- [ ] Integration tests
- [ ] Manual testing

## Checklist
- [ ] My code follows the project style guidelines
- [ ] I have performed a self-review
- [ ] I have commented hard-to-understand areas
- [ ] I have updated documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix/feature works
- [ ] New and existing tests pass locally

## Screenshots (if applicable)

## Related Issues
Closes #
```

## Best Practices

1. **Use feature branches** for all changes
2. **Write meaningful commit messages** following conventions
3. **Set up pre-commit hooks** for code quality
4. **Require PR reviews** before merging
5. **Keep PRs small** and focused
6. **Rebase before merging** for clean history
7. **Automate with CI/CD** pipelines

Google Antigravity helps generate proper commit messages and PR descriptions.

When to Use This Prompt

This git prompt is ideal for developers working on:

git applications requiring modern best practices and optimal performance
Projects that need production-ready git code with proper error handling
Teams looking to standardize their git development workflow
Developers wanting to learn industry-standard git patterns and techniques

By using this prompt, you can save hours of manual coding and ensure best practices are followed from the start. It's particularly valuable for teams looking to maintain consistency across their git implementations.

How to Use

Copy the prompt - Click the copy button above to copy the entire prompt to your clipboard
Paste into your AI assistant - Use with Claude, ChatGPT, Cursor, or any AI coding tool
Customize as needed - Adjust the prompt based on your specific requirements
Review the output - Always review generated code for security and correctness

💡 Pro Tip: For best results, provide context about your project structure and any specific constraints or preferences you have.

Best Practices

✓ Always review generated code for security vulnerabilities before deploying
✓ Test the git code in a development environment first
✓ Customize the prompt output to match your project's coding standards
✓ Keep your AI assistant's context window in mind for complex requirements
✓ Version control your prompts alongside your code for reproducibility

Frequently Asked Questions

Can I use this git prompt commercially?

Yes! All prompts on Antigravity AI Directory are free to use for both personal and commercial projects. No attribution required, though it's always appreciated.

Which AI assistants work best with this prompt?

This prompt works excellently with Claude, ChatGPT, Cursor, GitHub Copilot, and other modern AI coding assistants. For best results, use models with large context windows.

How do I customize this prompt for my specific needs?

You can modify the prompt by adding specific requirements, constraints, or preferences. For git projects, consider mentioning your framework version, coding style, and any specific libraries you're using.

Related Prompts

💬 Comments

Loading comments...

# Git Workflow Patterns for Google Antigravity Master effective Git workflows for seamless team collaboration with Google Antigravity IDE. ## Branch Naming Conventions ```bash # Feature branches feature/user-authentication feature/add-payment-integration feature/JIRA-123-update-dashboard # Bug fix branches fix/login-redirect-issue fix/JIRA-456-null-pointer-error hotfix/critical-security-patch # Other branch types release/v2.1.0 docs/api-documentation refactor/database-queries test/integration-tests ``` ## Commit Message Format ```bash # Conventional Commits format <type>(<scope>): <description> [optional body] [optional footer(s)] # Types feat: New feature fix: Bug fix docs: Documentation only style: Formatting, missing semi-colons refactor: Code change that neither fixes nor adds perf: Performance improvement test: Adding missing tests chore: Build process or auxiliary tools ci: CI configuration files # Examples feat(auth): add Google OAuth integration - Configure OAuth client - Add callback handler - Store tokens securely Closes #123 fix(api): resolve race condition in user creation The user creation endpoint could create duplicate users when requests arrived simultaneously. Added database locking to prevent this. Fixes #456 ``` ## Git Hooks with Husky ```typescript // package.json { "scripts": { "prepare": "husky install", "lint": "eslint . --ext .ts,.tsx", "format": "prettier --write .", "test": "vitest run", "typecheck": "tsc --noEmit" }, "lint-staged": { "*.{ts,tsx}": [ "eslint --fix", "prettier --write" ], "*.{json,md}": [ "prettier --write" ] } } // .husky/pre-commit #!/usr/bin/env sh . "$(dirname -- "$0")/_/husky.sh" npx lint-staged // .husky/commit-msg #!/usr/bin/env sh . "$(dirname -- "$0")/_/husky.sh" npx --no -- commitlint --edit $1 // commitlint.config.js module.exports = { extends: ["@commitlint/config-conventional"], rules: { "type-enum": [ 2, "always", ["feat", "fix", "docs", "style", "refactor", "perf", "test", "chore", "ci"] ], "subject-case": [2, "always", "lower-case"], "subject-max-length": [2, "always", 72] } }; ``` ## PR Template ```markdown  ## Description Brief description of changes ## Type of Change - [ ] Bug fix - [ ] New feature - [ ] Breaking change - [ ] Documentation update ## How Has This Been Tested? - [ ] Unit tests - [ ] Integration tests - [ ] Manual testing ## Checklist - [ ] My code follows the project style guidelines - [ ] I have performed a self-review - [ ] I have commented hard-to-understand areas - [ ] I have updated documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix/feature works - [ ] New and existing tests pass locally ## Screenshots (if applicable) ## Related Issues Closes # ``` ## Best Practices 1. **Use feature branches** for all changes 2. **Write meaningful commit messages** following conventions 3. **Set up pre-commit hooks** for code quality 4. **Require PR reviews** before merging 5. **Keep PRs small** and focused 6. **Rebase before merging** for clean history 7. **Automate with CI/CD** pipelines Google Antigravity helps generate proper commit messages and PR descriptions.