What problem does it solve? Team members often ask how the release process works — what branch to create, how version tags are numbered, what to do when a bug appears during RC, or how to handle a hotfix after deployment. This Skill answers those questions by explaining the team's git branching and deployment conventions, so the AI can give consistent, accurate guidance instead of guessing. ## Core Features & Use Cases - Branching Model Reference: Documents fixed branches (main, develop) and temporary branches (feat/, rc/, fix/, hotfix/) with their naming rules, base branches, and lifecycles. - Version Tag Rules: Explains the Major.Minor.Hotfix.Test scheme — Minor increments per release, Hotfix per emergency fix, Test per RC fix merge. - Three-Phase Flow: Covers development (feat branches into develop), RC stabilization (fix branches, Test tag bumps, reverting excluded issues), and deployment (tag first, verify, then merge to main and develop). - Use Case: A developer asks "RC 중에 버그 나면 어떻게 해?" and the Skill explains to branch fix/{issue-key}-{N} from the RC branch, open a PR against it, and bump the Test version after merging. ## Quick Start Ask the assistant to explain the team's deployment flow or what the rc/ and hotfix/ branch naming rules mean.
