What problem does it solve? Teams struggle with inconsistent Git practices: unclear branching strategies, vague commit messages, messy merge conflicts, and risky history rewrites. This Skill provides concrete patterns for choosing a branching model, writing conventional commits, resolving conflicts, and managing releases. ## Core Features & Use Cases - Branching Strategy Selection: Compares GitHub Flow, trunk-based development, and GitFlow with decision criteria based on team size and release cadence. - Commit & PR Conventions: Provides Conventional Commits format, PR templates, and code review checklists for consistent collaboration. - Conflict Resolution & History Management: Covers merge vs rebase trade-offs, conflict resolution commands, stash workflows, and safe undo operations. - Use Case: A team lead setting up a new repository can use this Skill to pick GitHub Flow, enforce conventional commit messages, and document a PR review checklist for contributors. ## Quick Start Ask the assistant to recommend a Git branching strategy and commit message convention for your team's project.