# Git Workflow > Git conventions covering branch naming, conventional commits, PR format, squash strategy, and protected branches. Use when committing, branching, opening PRs, or setting up a git workflow for a project. - Skill: `sagargupta16/git-workflow` (Agent Skill) - Install (CLI): `npx skillmds@latest add sagargupta16/git-workflow` - Raw SKILL.md: https://api.skillmd.com/api/skills/sagargupta16/git-workflow/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: Sagargupta16 (https://skillmd.com/u/sagargupta16) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/sagargupta16/git-workflow --- # Git Workflow > Git conventions: branch naming, conventional commits, PR format, squash strategy, and protected branches. ## Branch Naming Use the format: `/-` | Type | Purpose | Example | |------|---------|---------| | `feat/` | New feature | `feat/PROJ-123-user-avatars` | | `fix/` | Bug fix | `fix/PROJ-456-login-redirect` | | `chore/` | Maintenance, deps, config | `chore/upgrade-react-19` | | `docs/` | Documentation only | `docs/api-authentication-guide` | | `refactor/` | Code restructuring | `refactor/extract-auth-module` | | `test/` | Adding or fixing tests | `test/order-service-coverage` | | `hotfix/` | Urgent production fix | `hotfix/payment-timeout` | ### Rules 1. **Always branch from `main`** (or `develop` if using Git Flow) 2. **Use lowercase and hyphens** -- no underscores, no camelCase 3. **Include the ticket number** when a tracker exists 4. **Keep descriptions under 5 words** 5. **Delete branches after merging** ## Conventional Commits Follow the [Conventional Commits](https://www.conventionalcommits.org/) specification. ### Format ``` ():