Git Workflow Designer

## ROLE
You are a DevOps engineer specializing in Git workflows and team collaboration.

## CONTEXT
I need a Git workflow for:

**Team Details:**
- Team Size: [TEAM_SIZE]
- Release Frequency: [RELEASE_FREQUENCY]
- Current Workflow: [CURRENT_WORKFLOW]
- CI/CD Platform: [CI_CD_PLATFORM]
- Deployment Strategy: [DEPLOYMENT_STRATEGY]

## TASK
Design complete Git workflow:

### 1. BRANCHING STRATEGY
```
main (production)
  └── develop (staging)
        ├── feature/[TICKET]-description
        ├── bugfix/[TICKET]-description
        └── hotfix/[TICKET]-description
```

### 2. BRANCH NAMING CONVENTION
| Type | Pattern | Example |
|------|---------|---------|
| Feature | feature/[TICKET]-short-desc | feature/PROJ-123-user-auth |
| Bugfix | bugfix/[TICKET]-short-desc | bugfix/PROJ-456-login-fix |
| Hotfix | hotfix/[TICKET]-short-desc | hotfix/PROJ-789-critical-fix |
| Release | release/v[VERSION] | release/v1.2.0 |

### 3. COMMIT MESSAGE CONVENTION
```
type(scope): description

[optional body]

[optional footer]
```

Types: feat, fix, docs, style, refactor, test, chore

Examples:
- feat(auth): add password reset functionality
- fix(api): resolve rate limiting issue
- docs(readme): update installation instructions

### 4. PR/MERGE REQUEST TEMPLATE
```markdown
## Description
[What does this PR do?]

## Type of Change
- [ ] Feature
- [ ] Bug fix
- [ ] Refactor
- [ ] Documentation

## Testing
- [ ] Unit tests added/updated
- [ ] Manual testing completed

## Checklist
- [ ] Code follows style guidelines
- [ ] Self-review completed
- [ ] Documentation updated
```

### 5. CODE REVIEW GUIDELINES
- Minimum reviewers: [number]
- Required checks: [list]
- Review focus areas: [list]

### 6. RELEASE PROCESS
1. Create release branch from develop
2. Update version numbers
3. Generate changelog
4. Merge to main
5. Tag release
6. Deploy to production
7. Merge back to develop

### 7. AUTOMATION (CI/CD)
```yaml
[CI_WORKFLOW_CONFIG]
```

## RULES
- Protect main and develop branches
- Require PR reviews
- Run tests before merge
- Use semantic versioning
- Keep branches short-lived
- Delete merged branches