What problem does it solve? Teams often struggle with inconsistent branch naming, messy commit histories, and painful merge conflicts. This Skill provides a structured Git workflow covering branching strategies, commit conventions, and conflict resolution so your repository history stays clean and your main branch stays deployable. ## Core Features & Use Cases - Branching Strategies: Compare Git Flow, GitHub Flow, and Trunk Based Development with standardized branch naming prefixes like feature/, fix/, and hotfix/. - Conventional Commits: Enforce the type(scope): description format (feat, fix, refactor, chore) with rules for atomic commits and clear messages. - Merge & Conflict Resolution: Guidance on merge vs rebase vs squash merge, plus step-by-step conflict resolution and abort procedures. - Use Case: A developer finishing a feature branch can follow the checklist to squash-merge into main, write a compliant commit message like feat(auth): add OAuth2 login support, and delete the branch afterward. ## Quick Start Ask the agent to review your current Git branching and commit practices and recommend a workflow following the git_workflow conventions.