# Git Workflow > Git workflow management — use when the user mentions git, conventional commits, commit quality, branch management, worktree operations, GitFlow, changelog generation, semantic versioning, release notes, backlog management, or issue tracking integration. NOT for CI/CD pipelines or pipeline YAML (use cicd-pipelines), NOT for non-git workflow orchestration (use skillstack-workflows or multi-agent-patterns), NOT for code review content or PR quality assessment (use code-review). - Skill: `viktorbezdek/git-workflow` (Agent Skill, multi-file: 30 files) - Install (CLI): `npx skillmds@latest add viktorbezdek/git-workflow` - Raw SKILL.md: https://api.skillmd.com/api/skills/viktorbezdek/git-workflow/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Product & Planning - Author: viktorbezdek (https://skillmd.com/u/viktorbezdek) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/viktorbezdek/git-workflow --- # Git Workflow - Comprehensive Git Management Skill Unified skill for commit management, branch workflows, worktree operations, and story backlog management. ## When to Use / Not Use **Use when:** - Writing, validating, or reviewing commit messages for conventional commits compliance - Grouping changed files into logical atomic commits - Managing feature branches and worktrees with GitFlow conventions - Generating changelogs from commit history - Calculating next semantic version from commit types - Managing a hierarchical story backlog linked to code changes - Running `/commit`, `/validate`, `/changelog`, `/version` commands **Do NOT use when:** - CI/CD pipeline configuration or deployment YAML -> use `cicd-pipelines` - Non-git workflow orchestration -> use `skillstack-workflows` or `multi-agent-patterns` - Code review content (security, performance, design) -> use `code-review` ## Decision Tree ``` What Git workflow task do you need? ├── Write commits │ ├── Single logical change -> /commit (auto-analyze staged diff) │ ├── Multiple changed files, unclear grouping -> python scripts/group-files.py --analyze │ ├── Validate message format -> /validate "feat(auth): add JWT refresh" │ └── Amend/fix last commit -> /fix ├── Branch management │ ├── New feature branch -> feature/{name}, use GitFlow conventions │ ├── New fix branch -> fix/{name} │ ├── Critical production fix -> hotfix/{name} from main │ └── Need parallel work -> git worktree (scripts/create_worktree.sh) ├── Release workflow │ ├── Generate changelog -> python scripts/changelog.py --version X.Y.Z │ ├── Determine next version -> python scripts/version.py --verbose │ │ ├── Has BREAKING CHANGE -> major (X.0.0) │ │ ├── Has feat commits -> minor (0.X.0) │ │ └── Only fix/other -> patch (0.0.X) │ └── Clean up merged worktrees -> scripts/cleanup_worktrees.sh --merged ├── Story backlog │ ├── Initialize tree -> "Initialize story tree" │ ├── Generate stories -> "Generate stories for [epic-id]" │ ├── View tree -> python scripts/tree-view.py --show-capacity │ └── Update from commits -> "Update story tree" ├── Issue integration │ ├── Sync issues -> python scripts/issue-tracker.py sync assigned │ └── Suggest refs for staged changes -> python scripts/issue-tracker.py suggest-refs └── Not a Git workflow question? -> See related skills ``` ## Part 1: Commit Management ### Conventional Commits Format ``` ():