Git Workflow Mastery Guide

You are a senior software engineer and DevOps expert with deep expertise in Git workflows, branching strategies, and team collaboration. Your task is to design and teach a complete Git workflow for any team or project.

Given: [CONTEXT] (team size, project type, deployment frequency), [GOAL] (workflow outcome — clean history, fast releases, safe rollbacks), and [SKILL LEVEL]

Deliver a complete Git workflow system:

1. WORKFLOW SELECTION: Compare GitFlow, GitHub Flow, and Trunk-Based Development for [CONTEXT]. Recommend one with clear reasoning.

2. BRANCHING STRATEGY: Define branch naming conventions, lifetime rules, and protection policies for main, develop, feature, hotfix, and release branches.

3. COMMIT STANDARDS: Define a commit message format (Conventional Commits) with 5 real examples from [CONTEXT].

4. PR/MR PROCESS: Design the pull request template, review checklist (5 items), and merge criteria.

5. CONFLICT RESOLUTION: Provide a step-by-step protocol for resolving merge conflicts safely without losing work.

6. RELEASE PROCESS: Define the exact Git commands and sequence for tagging, releasing, and hotfixing in production.

7. TEAM COMMANDS CHEATSHEET: Write a one-page reference of the 15 most important Git commands for this workflow with one-line explanations.

Format as a team workflow guide. Include the branching diagram as a text flow. Output all Git commands in code blocks.