What problem does it solve? Teams struggle with inconsistent commit histories, messy pull requests, merge conflicts, and unclear branching strategies, leading to broken main branches and slow code review cycles. ## Core Features & Use Cases - Branching Strategies: Provides decision guidance between trunk-based development and Git Flow, with rules for branch lifetime, merging, and deployment. - Commit & PR Standards: Enforces Conventional Commits format, breaking change notation, and structured pull request templates with review checklists. - Git Operations Reference: Covers interactive rebase, merge conflict resolution, stashing, and safe undo patterns including reflog recovery. - Repository Hardening: Documents branch protection rules, Git hooks with Husky and lint-staged, and commitlint configuration. - Use Case: A developer about to merge a feature branch can follow the rebase and conflict resolution steps, write a compliant commit message, and open a PR that passes branch protection checks. ## Quick Start Ask the assistant to help clean up your local commits with an interactive rebase and write a conventional commit message before opening a pull request.