What problem does it solve? Teams working on shared repositories often end up with inconsistent branch names, lost track of feature iterations, and stale merged branches cluttering the repo. This Skill enforces a consistent branch naming convention, tracks feature version history across branches, and manages safe branch cleanup. ## Core Features & Use Cases - Convention-Based Branch Creation: Detects intent (feature, fix, chore, refactor, release, hotfix) and generates compliant names like feature/date-picker-v2, with automatic version suffix detection for iterated features. - Version History Tracking: Answers "what version is this feature?" by listing all matching branches with merge status and last-commit dates. - Safe Branch Cleanup: Lists branches fully merged into main and deletes only what the user explicitly selects, using git branch -d to prevent deleting unmerged work. - Use Case: A developer asks to rebuild the data-table component. The Skill detects existing feature/data-table and feature/data-table-v2 branches, suggests feature/data-table-v3, validates the base branch is main, and creates it with upstream tracking. ## Quick Start Ask the assistant to create a new feature branch for rebuilding the date picker component and it will suggest a versioned, convention-compliant name.