git-workflow
Installation
SKILL.md
Git Workflow
Effective version control is not just about tracking changes -- it is about enabling teams to collaborate predictably, release confidently, and maintain a history that tells a coherent story. The right workflow depends on team size, release cadence, and how much process the project can absorb without slowing down.
Choosing a Branching Strategy
No single branching model fits every team. The right choice depends on how often you release, how large your team is, and how much ceremony you can tolerate.
Strategy Comparison
| Strategy | Release Cadence | Team Size | Complexity | Best For |
|---|---|---|---|---|
| Trunk-Based | Continuous (multiple per day) | Any (works best with strong CI) | Low | SaaS, cloud-native, teams with mature CI/CD |
| GitHub Flow | On-demand (per merged PR) | Small to medium | Low | Web apps, startups, teams wanting simplicity |
| Git Flow | Scheduled / versioned releases | Medium to large | High | Packaged software, mobile apps, multiple supported versions |
| GitLab Flow | Environment-promoted | Medium to large | Medium | Teams needing environment-specific branches (staging, production) |