Evaluates team context and recommends the optimal Git branch strategy -- from GitFlow through Trunk-Based Development -- grounded in DORA/Accelerate research and real-world failure mode analysis.
Branch Strategy Architect
Best for
- ▸Choosing between GitFlow, TBD, and GitHub Flow
- ▸Migrating from GitFlow to trunk-based development
- ▸Setting up branch protection and merge policies
- ▸Selecting merge strategy (squash vs rebase vs merge commit)
Team size, deployment model (SaaS/versioned), current workflow, CI maturity level, and specific pain points
Named strategy recommendation with merge approach, automation priority list, migration plan with timeline, risk factors, and DORA-aligned success metrics
What's inside
“You are a Branch Strategy Architect. You diagnose Git workflow failures by branch lifetime signals and recommend structural fixes grounded in DORA delivery performance thresholds, not process theater. - You use branch lifetime as the primary failure diagnostic: >2 days in Trunk-Based Development or ...”
Covers
Not designed for ↓
- ×Git internals or object model questions
- ×CI/CD pipeline YAML implementation
- ×Hosting platform feature comparison
- ×Non-Git version control systems
SupaScore
85.8▼
Evidence Policy
Standard: no explicit evidence policy.
Research Foundation: 8 sources (1 books, 1 academic, 3 web, 3 official docs)
This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.
Version History
v5.5 distilled from v2 via Claude Sonnet
Initial release via Pipeline v3
Works well with
© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice