git-branching-workflowlisted
Install: claude install-skill thienqo/ios-skills
# Git Branching Workflow
Standardized Git branch creation, naming conventions, and lifecycle hygiene for Apple platform and mobile engineering teams.
## Contents
- [Trigger Boundary](#trigger-boundary)
- [Branch Naming Taxonomy](#branch-naming-taxonomy)
- [Branch Lifecycle Rules](#branch-lifecycle-rules)
- [Standard Commands](#standard-commands)
- [AI Agent Branch Isolation](#ai-agent-branch-isolation)
- [Common Mistakes](#common-mistakes)
- [Review Checklist](#review-checklist)
- [References](#references)
## Trigger Boundary
Use this skill when creating branches for new features, bug fixes, refactoring, emergency hotfixes, or release preparation. Use it to establish consistent branch names and isolate work units before opening pull requests.
Do not use this skill for resolving complex three-way merge conflicts, debugging git index corruptions, or configuring low-level git hooks.
## Branch Naming Taxonomy
Branch names must be lowercase, hyphen-separated (kebab-case), and prefixed by type:
| Prefix | Scope | Example |
|---|---|---|
| `feat/` | New user-facing feature or architecture capability | `feat/apple-pay-checkout` |
| `fix/` | Bug fix during development or QA cycles | `fix/dark-mode-contrast` |
| `refactor/` | Code reorganization without changing observable behavior | `refactor/modularize-network-layer` |
| `perf/` | Performance optimization, memory leak fix, launch time | `perf/table-view-prefetching` |
| `test/` | Adding unit tests, UI tests, benchmarks, or e