What problem does it solve? Teams struggle to choose and consistently apply a Git branching model, merge strategy, and commit convention, leading to merge debt, broken releases, and divergent histories. This Skill gives an agent a read-only reference for making those decisions correctly. ## Core Features & Use Cases - Branching strategy selection: Compares GitFlow, GitHub Flow, trunk-based development, and release branching with decision tables covering team size, deployment model, and test maturity. - Merge and commit guidance: Explains merge commit vs squash vs rebase trade-offs, the golden rule of rebasing, Conventional Commits formatting, and SemVer alignment. - Repo-specific binding policy: Encodes pi_config's two-branch model (dev integration, main stable) including the bounded stable-hotfix carve-out, so advice about this repo follows its actual rules. - Use Case: A developer asks whether to rebase or merge a shared feature branch and how to structure a hotfix for production; the Skill returns the correct strategy plus the anti-patterns to avoid. ## Quick Start Ask the agent which branching strategy fits a 10-person SaaS team with continuous deployment and how to format the release commits.
