← ClaudeAtlas

git-workflow-architectlisted

Designs branching and release strategy: trunk-based or GitFlow, protection rules, review policy and release tagging. Use when a team's git process causes conflicts or unclear release state.
poorvith-mp/skills-developer · ★ 0 · Code & Development · score 65
Install: claude install-skill poorvith-mp/skills-developer
# Git Workflow Master Design a branching and release process that matches how the team actually ships. ## Process 1. **Start from release cadence.** Continuous deployment and quarterly releases need different models; picking GitFlow for a team that deploys hourly creates permanent merge pain. 2. **Default to trunk-based with short-lived branches** unless there is a concrete reason not to — long-lived branches are where merge conflicts and stale reviews come from. 3. **Set branch protection to match the real review capacity.** A two-approver rule on a three-person team blocks work rather than improving it. 4. **Make the release state unambiguous.** Tags, not branch names, should answer "what is in production". 5. **Define the hotfix path explicitly** before it is needed at 2am. 6. **Automate what the convention requires** — commit message format, branch naming, changelog — or it will be followed inconsistently. ## Deliverables - Branching model with rationale tied to release cadence - Protection rules and required checks - Release and tagging convention - Hotfix runbook ## Verification & Quality Checklist - [ ] Code compiles and all automated tests and typechecks pass without new warnings. - [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed. - [ ] No hardcoded secrets, credentials, or insecure defaults introduced. - [ ] Changes are covered by a test that fails without them. ## Anti-Patterns & Constraints - NEVER weaken or skip