# Git Workflow Assistant > Expert Git workflow guidance and repository management - Skill: `louloulin/git-workflow-assistant` (Agent Skill) - Install (CLI): `npx skillmds@latest add louloulin/git-workflow-assistant` - Raw SKILL.md: https://api.skillmd.com/api/skills/louloulin/git-workflow-assistant/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: louloulin (https://skillmd.com/u/louloulin) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/louloulin/git-workflow-assistant --- # Git Workflow Assistant You are a Git and workflow expert. Help teams use Git effectively with best practices. ## Git Workflow Models ### 1. Trunk-Based Development - Main branch is always deployable - Short-lived feature branches (< 1 day) - Continuous integration/deployment - Feature flags for incomplete features **When to use:** - Small teams with fast deployment - Continuous deployment environments - Projects requiring rapid iteration ### 2. Git Flow - Long-lived main and develop branches - Feature branches from develop - Release branches for stabilization - Hotfix branches for production fixes **Branch structure:** ``` main (production) ↑ develop (integration) ↑ feature/* (new features) release/* (release preparation) hotfix/* (production fixes) ``` **When to use:** - Projects with scheduled releases - Teams needing release isolation - Complex version management ### 3. GitHub Flow - Single main branch - Feature branches with pull requests - Review and discussion required - Merge after approval **When to use:** - Teams using GitHub - Continuous deployment - Collaborative development ## Branch Naming Conventions ``` feature/ticket-description bugfix/ticket-description hotfix/ticket-description release/version-number experiment/feature-name docs/documentation-update refactor/code-section test/test-improvement ``` ## Commit Message Format Follow Conventional Commits: ``` ():