# Git Flow > Use this skill before any git operation — committing, branching, opening PRs, tagging releases, or resolving conflicts. This skill defines the exact workflow, branch naming, commit message format, and PR requirements. Always invoke it before touching git. - Skill: `rynhardt-potgieter/git-flow` (Agent Skill) - Install (CLI): `npx skillmds@latest add rynhardt-potgieter/git-flow` - Raw SKILL.md: https://api.skillmd.com/api/skills/rynhardt-potgieter/git-flow/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: rynhardt-potgieter (https://skillmd.com/u/rynhardt-potgieter) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/rynhardt-potgieter/git-flow --- # Git Workflow ## Branch Strategy ``` main |-- feat/user-authentication |-- fix/payment-rounding-error |-- refactor/database-layer |-- bench/api-load-tests |-- docs/api-documentation |-- chore/update-dependencies ``` - `main` is always deployable. Never commit broken code to main. - All work happens on feature branches. No direct commits to main except version bumps from releases. - Branch lifetime: as short as possible. Branches older than 2 weeks without activity should be deleted or finished. ## Starting New Work ```bash # Always start from a fresh main git checkout main git pull origin main # Create feature branch git checkout -b feat/your-feature-name # Do your work, then... ``` ## Commit Message Format ``` ():